# Blocking transform
##  Blocking transform
### Description
The Blocking transform blocks all output until the very last row is received from the previous transform.
{% hint style="success" %}
The transform blocks until it gets the last row. It does **not** block until the previous transform is finished 100% which is functionality found in the other transform [Blocking until transforms finish](/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/blockuntiltransformsfinish.md).
{% endhint %}
At that point, the last row is sent to the next transform or the complete input is sent off to the next transform. Use the Blocking transform for triggering plugins, stored procedures, Java scripts, … or for synchronization purposes.
| Hop Engine | ✓ |
| ---------- | ------------ |
| Spark | ? |
| Flink | ? |
| Dataflow | ? |
### Options
| Option | Description |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Transform name | Name of the transform; this name has to be unique in a single pipeline. |
| Pass all rows? | Determines whether to pass one row or all rows |
| Spool directory | The directory in which the temporary files are stored if needed; the default is the standard temporary directory for the system |
| Spool-file prefix | Choose a recognizable prefix to identify the files when they appear in the temp directory |
| Cache size | The more rows you can store in memory, the faster the transform works |
| Compress spool files? | Compresses temporary files when they are needed |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/blockingtransform.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.