[jira] [Resolved] (IMPALA-4276) Non-default query options not always populated in runtime profile.

["Bikramjeet Vig (JIRA)" <ji...@apache.org>]

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

Bikramjeet Vig resolved IMPALA-4276.
------------------------------------
    Resolution: Fixed


IMPALA-4276: Profile displays non-default query options set by planner

Fix to populate the non-default query options set by planner in the
runtime profile.

Added a corresponding test case.

Change-Id: I08e9dc2bebb83101976bbbd903ee48c5068dbaab
Reviewed-on: http://gerrit.cloudera.org:8080/7419
Reviewed-by: Matthew Jacobs <mj...@cloudera.com>
Tested-by: Impala Public Jenkins

> Non-default query options not always populated in runtime profile.
> ------------------------------------------------------------------
>
>                 Key: IMPALA-4276
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4276
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.6.0, Impala 2.7.0, Impala 2.8.0
>            Reporter: Alexander Behm
>            Assignee: Bikramjeet Vig
>              Labels: ramp-up, supportability, usability
>
> Query options automatically set by the Impala planner appear to not be reported in the runtime profile under the non-default query options.
> Example query:
> {code}
> select * from functional.alltypes limit 1
> {code}
> The above query should trigger the single-node optimization and automatically set num_nodes=1, num_scanner_threads=1 and disable_codegen=true, but none of those changes are reported in the runtime profile under "Query Options (non default)".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)