[
https://issues.apache.org/jira/browse/IMPALA-12906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell reassigned IMPALA-12906:
--------------------------------------
Assignee: Joe McDonnell
> Incorporate run time scan range information into the tuple cache key
> --------------------------------------------------------------------
>
> Key: IMPALA-12906
> URL: https://issues.apache.org/jira/browse/IMPALA-12906
> Project: IMPALA
> Issue Type: Task
> Components: Backend, Frontend
> Affects Versions: Impala 4.4.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
>
> The cache key for tuple caching currently doesn't incorporate information
> about the scan ranges for the tables that it scans. This is important for
> detecting changes in the table and having different cache keys for different
> fragment instances that are assigned different scan ranges.
> To make this deterministic for mt_dop, we need mt_dop to assign scan ranges
> deterministically to individual fragment instances rather than using the
> shared queue introduced in IMPALA-9655.
> One way to implement this is to collect information about the scan nodes that
> feed into the tuple cache and pass that information over to the tuple cache
> node. At runtime, it can hash the scan ranges assigned to those scan nodes
> and incorporate that into the cache key.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
