[
https://issues.apache.org/jira/browse/KUDU-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308872#comment-15308872
]
Dan Burkert commented on KUDU-1306:
-----------------------------------
The non-covering range partitioning work is starting to land, and we don't have
a story around forwards compatibility. Old clients (0.9 and below) will not be
able to use a non-covered range partition without entering an RPC loop. We
need to figure out if this is worth fixing. The obvious fix of adding a flag
to the {{GetTableLocations}} RPC to specify whether a client can support
non-covered range partitions will not work, since the old clients enter an RPC
loop when the {{GetTableLocations}} RPC fails. Having the master track which
tables have non-covered range partitions and failing during {{GetTableSchema}}
may work.
> timeseries features and improvements
> ------------------------------------
>
> Key: KUDU-1306
> URL: https://issues.apache.org/jira/browse/KUDU-1306
> Project: Kudu
> Issue Type: New Feature
> Components: api, client, master
> Reporter: Dan Burkert
> Assignee: Dan Burkert
>
> This is a tracking ticket for improvements and features to Kudu for enabling
> timeseries use cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
