[ https://issues.apache.org/jira/browse/KUDU-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001233#comment-17001233 ]
Todd Lipcon commented on KUDU-3032: ----------------------------------- The issue is that we seem to determine the "missing columns" for a scan prior to running the "OptimizeScanSpec()" function. > key columns unnecessarily selected when predicate is converted to range > ----------------------------------------------------------------------- > > Key: KUDU-3032 > URL: https://issues.apache.org/jira/browse/KUDU-3032 > Project: Kudu > Issue Type: Bug > Components: perf > Affects Versions: 1.11.1 > Reporter: Todd Lipcon > Priority: Major > > When a predicate applies to leading primary key columns, the tablet service > optimizes it into a range scan and removes those predicates from the > ScanSpec. However, the current behavior (seemingly going back to when this > was implemented) does not actually prevent those key columns from being read > from disk. This has a negative performance impact, particularly when the keys > are large or inefficient to decompress. -- This message was sent by Atlassian Jira (v8.3.4#803005)