You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Dan Burkert (JIRA)" <ji...@apache.org> on 2016/04/01 22:03:25 UTC
[jira] [Commented] (KUDU-1148) Allow to set exclusive column
predicates
[ https://issues.apache.org/jira/browse/KUDU-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222255#comment-15222255 ]
Dan Burkert commented on KUDU-1148:
-----------------------------------
On the Java side this is fixed by 16c03cda041f901247d83bf37c1958697a3a96dc (which made it in to 0.8), but the C++ side still needs to expose it. The internals support exclusive ops, but it isn't piped through to the client API.
> Allow to set exclusive column predicates
> ----------------------------------------
>
> Key: KUDU-1148
> URL: https://issues.apache.org/jira/browse/KUDU-1148
> Project: Kudu
> Issue Type: New Feature
> Components: tserver
> Affects Versions: Public beta
> Reporter: David Alves
> Assignee: Dan Burkert
>
> We currently only support setting inclusive (>=,<=) predicates. We should also support exclusive ones (<,>). This provides the user with a mixed experience as apparently similar scans might have very different performance profiles.
> We think this isn't too hard though the associated testing might be a couple days work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)