[jira] [Resolved] (IMPALA-5784) Separate planner-set query options from user set ones in the profile

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

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

Bikramjeet Vig resolved IMPALA-5784.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0

https://github.com/cloudera/Impala/commit/81be352761e6267d561d7bf4119688b39abc7e3f

IMPALA-5784: Separate planner and user set query options in profile
This separation will help the user better understand the query
runtime profile.

Testing:
Modified an existing test case.

Change-Id: Ibfc7832963fa0bd278a45c06a5a54e1bf40d8876
Reviewed-on: http://gerrit.cloudera.org:8080/7721
Reviewed-by: Matthew Jacobs <mj...@cloudera.com>
Reviewed-by: Dan Hecht <dh...@cloudera.com>
Tested-by: Impala Public Jenkins

> Separate planner-set query options from user set ones in the profile
> --------------------------------------------------------------------
>
>                 Key: IMPALA-5784
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5784
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.10.0
>            Reporter: Balazs Jeszenszky
>            Assignee: Bikramjeet Vig
>              Labels: supportability
>             Fix For: Impala 2.10.0
>
>
> IMPALA-4276 improved the tracking of query options by having the planner-set ones show up in the profile. These should have their own category to make it straightforward to decide whether the user or Impala is responsible for a particular setting.



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