>From the profile codegen is disabled for HDFS_SCAN_NODE (id=8) and not the
entire query.
If you wish to disable codegen run "set disable_codegen=1;" before
executing the query from impala-shell or add it to the connection string if
using JDBC.
HDFS_SCAN_NODE (id=8):(Total: 2.314ms, non-child: 2.314ms, %
non-child: 100.00%)
Hdfs split stats (<volume id>:<# splits>/<split lengths>):
2:1/14.28 KB
Hdfs Read Thread Concurrency Bucket: 0:0% 1:0% 2:0% 3:0%
File Formats: PARQUET/SNAPPY:3
ExecOption: Codegen enabled: 0 out of 1
On a side not I recommend trying out a more recent version of Impala
as a lot has improved since.
On Wed, Nov 8, 2017 at 12:13 AM, chen <[email protected]> wrote:
> I have a query,tooks a long time on codegen:
>
> CodeGen:(Total: 32m22s, non-child: 32m22s, % non-child: 100.00%)
> - CodegenTime: 0ns
> - CompileTime: 53.143ms
> - LoadTime: 58.680us
> - ModuleFileSize: 1.96 MB (2054956)
> - OptimizationTime: 32m22s
> - PrepareTime: 157.700ms
>
> but from the profile ,we can see that codegen is diabled for this query:
>
> ExecOption: Codegen enabled: 0 out of 1
>
> attached is the complete profile.
>
>
> can anyone help to firgure out a way to bypass.
>
>
> Chen
>
>
