[
https://issues.apache.org/jira/browse/KUDU-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008546#comment-17008546
]
ASF subversion and git services commented on KUDU-3032:
-------------------------------------------------------
Commit c767bd1149757094d8df96eaca879c06a5c1b648 in kudu's branch
refs/heads/master from triplesheep
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=c767bd1 ]
KUDU-3032 Prevent selecting unnecessarily columns after scan optimization
Not only those key columns which can convert to range but also
those non-nullable columns which can optimize with IS NOT NULL
predicates.
Change-Id: I82c30c5272b6fc114b710df9d6c31d5d1e319e31
Reviewed-on: http://gerrit.cloudera.org:8080/14945
Tested-by: Kudu Jenkins
Reviewed-by: Adar Dembo <a...@cloudera.com>
> 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
> Assignee: ZhangYao
> 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)
