[jira] [Commented] (KUDU-1644) Simplify IN-list predicate values based on tablet partition key or rowset PK bounds

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262713#comment-17262713 ] 

ASF subversion and git services commented on KUDU-1644:
-------------------------------------------------------

Commit 83b8caf4f1d60c021ef1e5a5f930847fb96c5ff4 in kudu's branch refs/heads/master from ningw
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=83b8caf ]

KUDU-1644 use range partition info for pruning

When pruning in-list predicate values, range partition can also be taken
into consideration.

Change-Id: I3f14f543cffd44f090026f344c9b06af13ea2e10
Reviewed-on: http://gerrit.cloudera.org:8080/16903
Tested-by: Kudu Jenkins
Reviewed-by: Andrew Wong <aw...@cloudera.com>


> Simplify IN-list predicate values based on tablet partition key or rowset PK bounds
> -----------------------------------------------------------------------------------
>
>                 Key: KUDU-1644
>                 URL: https://issues.apache.org/jira/browse/KUDU-1644
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: perf, tablet
>            Reporter: Dan Burkert
>            Priority: Major
>         Attachments: image-2019-12-05-14-52-05-846.png, image-2019-12-05-14-52-18-487.png, image-2019-12-05-14-53-51-175.png, image-2019-12-05-14-53-57-741.png, image-2019-12-05-14-54-03-485.png
>
>
> When new scans are optimized by the tablet, the tablet's partition key bounds aren't taken into account in order to remove predicates from the scan.  One of the most important such optimizations is that IN-list predicates could remove values based on the tablet's constraints.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)