impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Hecht (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-5784 : Separate planner and user set query options in profile
Date Tue, 22 Aug 2017 21:25:29 GMT
Dan Hecht has posted comments on this change.

Change subject: IMPALA-5784 : Separate planner and user set query options in profile

Patch Set 1:

> > (1 comment)
 > Relying to Dan and Balasz:
 > It's actually hard to determine what gets set where using the
 > QueryOptions map thing we have right now, mostly because of how
 > inconsistent we are with default values. E.g. what if a property is
 > set in the session, then the planner sets it as well, but happens
 > to set it to the default value. Right now we can't even identify
 > that as a non-default query option.

I don't follow this. We're defining "non-default" query option to mean everything that doesn't
match the static query option value, right?

If so, why can't we just compare the query option values after planning and to the values
before planning, and print any differences as "planner set" (or whatever name).  And then
compare the query options before planning with the static defaults, remove anything we've
already printed as "planner set" and print those remaining differences as "manually set".

or are you saying that doing that is tricky due to the datastructures we currently have?

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: Ibfc7832963fa0bd278a45c06a5a54e1bf40d8876
Gerrit-PatchSet: 1
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Bikramjeet Vig <>
Gerrit-Reviewer: Balazs Jeszenszky <>
Gerrit-Reviewer: Bikramjeet Vig <>
Gerrit-Reviewer: Dan Hecht <>
Gerrit-Reviewer: Matthew Jacobs <>
Gerrit-HasComments: No

View raw message