[
https://issues.apache.org/jira/browse/KUDU-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675277#comment-15675277
]
Dan Burkert commented on KUDU-1750:
-----------------------------------
Thanks for the report, this is indeed a serious bug. It appears that the issue
is that the guards are checking that either the lower or upper bound match
instead of both (|| vs &&):
https://github.com/apache/kudu/blob/master/src/kudu/master/catalog_manager.cc#L1415.
I'll have a fix out soon, and figure out what kind of actions we need to take
since this might be considered a data loss bug.
> Drop range partition is not working as expected
> ------------------------------------------------
>
> Key: KUDU-1750
> URL: https://issues.apache.org/jira/browse/KUDU-1750
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 1.0.1
> Reporter: Dimitris Tsirogiannis
> Assignee: Dan Burkert
> Priority: Blocker
>
> There are several cases wrt drop range partitions that don't seem to work as
> expected.
> 1. Drop matches only the lower bound (may be correct but is confusing to
> users).
> - alter table foo add range partition 10 < values <= 20;
> - alter table foo drop range partition 10 < values < 30; <--- this works
> and deletes partition (10, 20] but I'd expect an error.
> 2.
> - alter table foo add range partition values < 10;
> - alter table foo add range partition 20 < values <= 30;
> - alter table foo drop range partition values < 10000; <--- this drops the
> range partition (,10).
> This is Impala syntax that will be introduced in IMPALA-2890 (not currently
> committed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
