[
https://issues.apache.org/jira/browse/KUDU-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Burkert updated KUDU-1647:
------------------------------
Description: We currently stop pushing predicates into the upper bound
range partition key and pushing predicates into upper-bound primary key when a
range predicate is encountered. I _think_ (although we should probably think
harder about this), that predicates could continue to be pushed if the
exclusive range predicate value is decremented to make an inclusive upper bound
predicate. (was: We currently stop pushing predicates into the upper bound
range partition key and pushing predicates into upper-bound primary key when a
range predicate is encountered. I *think* (although we should probably think
harder about this), that predicates could continue to be pushed if the
exclusive range predicate value is decremented to make an inclusive upper bound
predicate.)
> Improve range partition pruning and primary-key bound optimization with
> upper-bound range predicates on discrete typed columns
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: KUDU-1647
> URL: https://issues.apache.org/jira/browse/KUDU-1647
> Project: Kudu
> Issue Type: Sub-task
> Components: client, tablet
> Reporter: Dan Burkert
>
> We currently stop pushing predicates into the upper bound range partition key
> and pushing predicates into upper-bound primary key when a range predicate is
> encountered. I _think_ (although we should probably think harder about
> this), that predicates could continue to be pushed if the exclusive range
> predicate value is decremented to make an inclusive upper bound predicate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
