[KUDU-3384] DRS-level scan optimization leads to failed scans

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.17.0
• Fix Version/s: 1.17.0
• Component/s: tserver
• Assignee: YifanZhang
• Reporter: Alexey Serbin
• Created: 20/Jul/22 04:52
• Updated: 21/Jul/22 14:39
• Resolved: 21/Jul/22 14:39

Description

Recently, a new DRS-level optimization for scan operations has been introduced with changelist 936d7edc4.

The newly introduced DRS-level optimization leads to scan failures when all of the following turns true:

• all the primary key columns are of integer types
• the table has no hash partitioning
• the table contains a row with all primary key columns set to INT{x}_MAX correspondingly
• the scan request is to scan all the table's data

I suspect that some of the conditions above might be relaxed, but I have a test case that reproduces the issue as described.  See this gerrit review item for the reproduction scenario.

Issue Links

• is related to: IMPALA-11441 test_kudu_upsert failed with Kudu Illegal State error