[IGNITE-6624] SQL: IndexingQueryCacheFilter should use immediate partition data if possible

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.4
• Component/s: cache, sql
• Labels: performance
• Assignee: Vladimir Ozerov
• Reporter: Vladimir Ozerov
• Created: 13/Oct/17 11:19
• Updated: 02/Nov/17 11:49
• Resolved: 02/Nov/17 11:49

Description

We need to filter backup keys during query execution. Currently to achieve this we do the following:
1) Get row link
2) Materialize the row (!!!)
3) Create H2 row (H2 wrapping)
4) Then get key from H2 row (unwrapping)
5) Calculate partition through affinity function

What it might look like:
1) Get row link
2) Get partition from link

This ticket is to implement working with partitions rather than keys when possible,

Issue Links

• blocks: IGNITE-6626 SQL: Avoid materializing rows when possible
• is blocked by: IGNITE-6641 PageId handling improvement: PARTITION_ID masking
• is blocked by: IGNITE-6605 SQL: Merge and optimize backup query filter
• links to: GitHub Pull Request #2847