GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/13501
[SPARK-15759] [SQL] Fallback to non-codegen when fail to compile generated
code
## What changes were proposed in this pull request?
In case of any bugs in whole-stage codegen, the generated code can't be
compiled, we should fallback to non-codegen to make sure that query could run.
The batch mode of new parquet reader depends on codegen, can't be easily
switched to non-batch mode, so we still use codegen for batched scan (for
parquet). Because it only support primitive types and the number of columns is
less than spark.sql.codegen.maxFields (100), it should not fail.
## How was this patch tested?
Manual test it with buggy operator, it worked well.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davies/spark codegen_fallback
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13501.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13501
----
commit 550e3864a2b80184aaa818b5bff2fb246b7bf42d
Author: Davies Liu <[email protected]>
Date: 2016-06-03T00:29:13Z
whole stage fallback
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
