[
https://issues.apache.org/jira/browse/KUDU-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahesh Reddy updated KUDU-3515:
-------------------------------
Description:
When upgraded to Kudu 1.17.0 from any prior Kudu release, it's not possible to
drop an unbounded range in an already existing table that uses hash and range
partitioning scheme (for range and hash partitioning example, see [this
documentation
page|https://kudu.apache.org/docs/schema_design.html#hash-range-partitioning-example]).
Please note: the issue only manifests itself for unbounded ranges. Also, plain
range partitioned tables (i.e. not involving range and hash partitioning, just
range-partitioned without hash sub-partition for each range) are not affected.
Below are the steps to reproduce the issue as per the instructions posted by
the original reporter in a [message thread of the #kudu-general Slack
channel|https://getkudu.slack.com/archives/C0CPXJ3CH/p1695107377230829].
# Create table with range partition in Kudu 1.16.0 or any prior release:
{noformat}
sudo -u kudu kudu table create <master_rpc_addr> '{ "table_name":
"default.test_drop_partition", "schema": { "columns": [ { "column_name": "id",
"column_type": "INT32", "default_value": "1" }, { "column_name": "key",
"column_type": "INT64", "is_nullable": false }, { "column_name": "name",
"column_type": "STRING", "is_nullable": false } ], "key_column_names": ["id",
"key"] }, "partition": { "hash_partitions": [{"columns": ["id"], "num_buckets":
2, "seed": 8}], "range_partition": { "columns": ["key"], "range_bounds": [
{"upper_bound": {"bound_type": "exclusive", "bound_values": ["1000"]} }, {
"lower_bound": {"bound_type": "inclusive", "bound_values":
["1000"]},"upper_bound": {"bound_type": "exclusive", "bound_values": ["2000"]}
} ] } }, "num_replicas": 3 }'
{noformat}
# Upgrade to Kudu 1.17.0 and try dropping the unbounded range partition:
{noformat}
sudo -u kudu kudu table drop_range_partition <master_rpc_addr>
default.test_drop_partition [] [1000]
{noformat}
Dropping the range partition fails with the following message:
{noformat}
Invalid argument: no range partition to drop: VALUES < 1000
{noformat}
was:
When upgraded to Kudu 1.17.0 from any prior Kudu release, it's not possible to
drop an unbounded range in an already existing table that uses hash and range
partitioning scheme (for range and hash partitioning example, see [this
documentation
page|https://kudu.apache.org/docs/schema_design.html#hash-range-partitioning-example]).
Please note: the issue only manifests itself for unbounded ranges. Also, plain
range partitioned tables (i.e. not involving range and hash partitioninig, just
range-partitioned without hash sub-partition for each range) are not affected.
Below are the steps to reproduce the issue as per the instructions posted by
the original reporter in a [message thread of the \#kudu-general Slack
channel|https://getkudu.slack.com/archives/C0CPXJ3CH/p1695107377230829].
# Create table with range partition in Kudu 1.16.0 or any prior release:
{noformat}
sudo -u kudu kudu table create <master_rpc_addr> '{ "table_name":
"default.test_drop_partition", "schema": { "columns": [ { "column_name": "id",
"column_type": "INT32", "default_value": "1" }, { "column_name": "key",
"column_type": "INT64", "is_nullable": false }, { "column_name": "name",
"column_type": "STRING", "is_nullable": false } ], "key_column_names": ["id",
"key"] }, "partition": { "hash_partitions": [{"columns": ["id"], "num_buckets":
2, "seed": 8}], "range_partition": { "columns": ["key"], "range_bounds": [
{"upper_bound": {"bound_type": "exclusive", "bound_values": ["1000"]} }, {
"lower_bound": {"bound_type": "inclusive", "bound_values":
["1000"]},"upper_bound": {"bound_type": "exclusive", "bound_values": ["2000"]}
} ] } }, "num_replicas": 3 }'
{noformat}
# Upgrade to Kudu 1.17.0 and try dropping the unbounded range partition:
{noformat}
sudo -u kudu kudu table drop_range_partition <master_rpc_addr>
default.test_drop_partition [] [1000]
{noformat}
Dropping the range partition fails with the following message:
{noformat}
Invalid argument: no range partition to drop: VALUES < 1000
{noformat}
> Unable to drop unbounded range partition from an existing table after
> upgrading to 1.17.0 version
> -------------------------------------------------------------------------------------------------
>
> Key: KUDU-3515
> URL: https://issues.apache.org/jira/browse/KUDU-3515
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
>
> When upgraded to Kudu 1.17.0 from any prior Kudu release, it's not possible
> to drop an unbounded range in an already existing table that uses hash and
> range partitioning scheme (for range and hash partitioning example, see [this
> documentation
> page|https://kudu.apache.org/docs/schema_design.html#hash-range-partitioning-example]).
> Please note: the issue only manifests itself for unbounded ranges. Also,
> plain range partitioned tables (i.e. not involving range and hash
> partitioning, just range-partitioned without hash sub-partition for each
> range) are not affected.
> Below are the steps to reproduce the issue as per the instructions posted by
> the original reporter in a [message thread of the #kudu-general Slack
> channel|https://getkudu.slack.com/archives/C0CPXJ3CH/p1695107377230829].
> # Create table with range partition in Kudu 1.16.0 or any prior release:
> {noformat}
> sudo -u kudu kudu table create <master_rpc_addr> '{ "table_name":
> "default.test_drop_partition", "schema": { "columns": [ { "column_name":
> "id", "column_type": "INT32", "default_value": "1" }, { "column_name": "key",
> "column_type": "INT64", "is_nullable": false }, { "column_name": "name",
> "column_type": "STRING", "is_nullable": false } ], "key_column_names": ["id",
> "key"] }, "partition": { "hash_partitions": [{"columns": ["id"],
> "num_buckets": 2, "seed": 8}], "range_partition": { "columns": ["key"],
> "range_bounds": [ {"upper_bound": {"bound_type": "exclusive", "bound_values":
> ["1000"]} }, { "lower_bound": {"bound_type": "inclusive", "bound_values":
> ["1000"]},"upper_bound": {"bound_type": "exclusive", "bound_values":
> ["2000"]} } ] } }, "num_replicas": 3 }'
> {noformat}
> # Upgrade to Kudu 1.17.0 and try dropping the unbounded range partition:
> {noformat}
> sudo -u kudu kudu table drop_range_partition <master_rpc_addr>
> default.test_drop_partition [] [1000]
> {noformat}
> Dropping the range partition fails with the following message:
> {noformat}
> Invalid argument: no range partition to drop: VALUES < 1000
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
