# Operator fallback

Glossary, read 10 Nov 2026

**The short answer.** Operator fallback is what an accelerator does when it cannot run a Spark operator or expression: that part of the plan runs on regular Spark, and the rest runs on the accelerator. The job finishes with the same result. The part that fell back runs at plain Spark speed, and rows and columns may be converted at the boundary.

Fallback is the main reason one workload speeds up more than another. Jobs dominated by Python UDFs or unsupported expressions spend most of their time in fallback.

Each option reports it differently: a marker in the explain output, a tab in the Spark UI, or a setting such as spark.rapids.sql.explain=NOT_ON_GPU. Ask a vendor how to see it before you trust a benchmark.

## A sourced example

The Apache Gluten Velox backend limitations page lists known fallbacks: ANSI mode always falls back, and regexp functions use RE2, which has no lookaround, so affected expressions can differ from Spark.

## Sources

- Apache Gluten home page: https://gluten.apache.org/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://sparkaccelerationcompare.com/glossary/operator-fallback/
