> 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/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/adaptive-execution-layer-cp-landing-page.md).

# Adaptive Execution Layer

Pentaho uses an Adaptive Execution Layer (AEL) for running transformations with Spark. AEL adapts steps from the transformation you develop in PDI to use the native operator functions in Spark. This adaptation is necessary because the Spark engine runs big data transformations in the Hadoop cluster differently than the Pentaho engine. For example, the Spark engine may not require some fields in the PDI step, or it may require setting a precise value setting for an option. Also, null values must be adjusted because Spark processes null values differently than the Pentaho engine.

Some PDI steps commonly used in big data transformations are specifically coded to the Spark APIs for improved performance when using the Spark engine. To see whether the step you want to use has been optimized for distributed processing with Spark, refer the documentation for that step. You can also view the list of [Recommended PDI steps to use with Spark on AEL](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/adaptive-execution-layer-cp-landing-page/use-ael/recommended-pdi-steps-to-use-with-spark-on-ael-cp.md).

To decide whether the Spark engine or the Pentaho engine is the best choice for your transformation, you must know what cluster resources you have and the size of your data sets.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/adaptive-execution-layer-cp-landing-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
