[
https://issues.apache.org/jira/browse/KUDU-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3723:
--------------------------------
Affects Version/s: 1.17.1
> Dropping and adding back same range partition right away isn't working for
> certain table schemas
> ------------------------------------------------------------------------------------------------
>
> Key: KUDU-3723
> URL: https://issues.apache.org/jira/browse/KUDU-3723
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.17.0, 1.18.0, 1.17.1, 1.18.1
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
>
> For a Kudu table partitioned by both range and hash, the following sequence
> leads to the table being stuck in a limbo state where it cannot be opened or
> operated by any other means, effectively rendering it inaccessible:
> * adding a new range with custom hash partition scheme
> * immediately drop the newly added range
> * immediately try adding the same range again
> The reproduction scenario is available at
> http://gerrit.cloudera.org:8080/23778 It's 100% repeatable/reproducible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
