[jira] [Updated] (IMPALA-2689) Log every time codegen is disabled due to NYI

["Alex Rodoni (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Rodoni updated IMPALA-2689:
--------------------------------
    Docs Text:   (was: If there's a performance section on codegen, it might be useful to mention that codegen cannot be performed in all cases. The runtime profile indicates which operators were codegen'd.)

> Log every time codegen is disabled due to NYI
> ---------------------------------------------
>
>                 Key: IMPALA-2689
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2689
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.3.0
>            Reporter: Skye Wanderman-Milne
>            Assignee: Anuj Phadke
>            Priority: Minor
>              Labels: codegen, ramp-up, supportability
>             Fix For: Impala 2.10.0
>
>
> Sometimes a function cannot be codegen'd, even with codegen enabled, because some functionality is not implemented (e.g. we cannot codegen the Avro scanner if the file schema does not match the table schema, certain types are not implemented for aggregates). We should always print a message to the log explaining why this is the case, otherwise it's very difficult to figure out why codegen couldn't be used for a certain query. We already log in some cases but not all.
> In addition, we could also put these reasons in the runtime profile. Currently we only log if codegen is enabled on an operator, but it would be also be useful to see if it was disabled and why.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org