> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/use-hadoop-with-pentaho/big-data-issues/the-group-by-step-is-not-supported-in-a-single-threaded-transformation-engine.md).

# Group By step is not supported in a single threaded transformation engine

If you have a job that contains both a Pentaho MapReduce entry and a `Reducer` transformation with a Group by step, you may receive a `Step 'Group by' of type 'GroupBy' is not Supported in a Single Threaded Transformation Engine` error message. This error can occur if:

* An entire set of rows sharing the same grouping key are filtered from the transformation before the Group By step.
* The **Reduce single threaded** option in the Pentaho MapReduce entry's **Reducer** tab is selected.

To fix this issue, open the Pentaho MapReduce entry and deselect the **Reduce single threaded** option in the **Reducer** tab.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/10.2-install/use-hadoop-with-pentaho/big-data-issues/the-group-by-step-is-not-supported-in-a-single-threaded-transformation-engine.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.