[
https://issues.apache.org/jira/browse/IMPALA-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871766#comment-17871766
]
Michael Smith commented on IMPALA-13186:
----------------------------------------
I'm leaning towards adding another field to QUERY_OPT_FN and requiring that
every option categorize itself. We can start with whether it affects results.
> Tuple cache keys should incorporate information about related query options
> ---------------------------------------------------------------------------
>
> Key: IMPALA-13186
> URL: https://issues.apache.org/jira/browse/IMPALA-13186
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 4.5.0
> Reporter: Joe McDonnell
> Assignee: Michael Smith
> Priority: Major
>
> Currently, the tuple cache key does not include information from the query
> options. Many query options have no impact on the result of a query (e.g.
> idle_session_timeout) or are evaluated purely on the coordinator during
> planning (e.g. broadcast_bytes_limit).
> However, some query options can impact behavior either by controlling how
> certain things are calculated (e.g. decimal_v2) or controlling what
> conditions result in an error. Changing a query option can change the output
> of a query.
> We need some way to incorporate the relevant query options into the tuple
> cache key so there is no correctness issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
