[
https://issues.apache.org/jira/browse/IMPALA-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gaoxiaoqing updated IMPALA-11912:
---------------------------------
Description:
In https://issues.apache.org/jira/browse/IMPALA-4052, it supports cloning the
schema (including hash partitions) from kudu table after execute 'CREATE TABLE
$target_table LIKE $source_kudu_table'. But it don't support cloning range
partitions from source table if there is any. For example, the following range
partitions can't be cloned after execute 'create table
custom_hash_range_single_clone like custom_hash_range_single.'
{code:java}
create table custom_hash_range_single (id int, c2 int, primary key(id, c2))
partition by hash(id) partitions 3,
range (c2)
(
partition 0 <= values < 10
, partition 10 <= values < 20 hash partitions 2
, partition 20 <= values < 30 hash(c2) partitions 3
, partition 30 <= values < 40 hash(id) partitions 4
, partition 40 <= values < 50 hash(id, c2) partitions 5
)
stored as kudu; {code}
Consider supporting cloning range partitions in this jira.
was:
In https://issues.apache.org/jira/browse/IMPALA-4052, it supports cloning the
schema (including hash partitions) from kudu table after execute 'CREATE TABLE
$target_table LIKE $source_kudu_table'. But it don't support cloning range
partitions from source table if there is any.
For example, the following range partitions can be cloned after execute 'create
table custom_hash_range_single_clone like custom_hash_range_single.'
{code:java}
create table custom_hash_range_single (id int, c2 int, primary key(id, c2))
partition by hash(id) partitions 3,
range (c2)
(
partition 0 <= values < 10
, partition 10 <= values < 20 hash partitions 2
, partition 20 <= values < 30 hash(c2) partitions 3
, partition 30 <= values < 40 hash(id) partitions 4
, partition 40 <= values < 50 hash(id, c2) partitions 5
)
stored as kudu; {code}
> Add support for cloning range partitions from kudu table
> --------------------------------------------------------
>
> Key: IMPALA-11912
> URL: https://issues.apache.org/jira/browse/IMPALA-11912
> Project: IMPALA
> Issue Type: New Feature
> Reporter: gaoxiaoqing
> Priority: Minor
>
> In https://issues.apache.org/jira/browse/IMPALA-4052, it supports cloning the
> schema (including hash partitions) from kudu table after execute 'CREATE
> TABLE $target_table LIKE $source_kudu_table'. But it don't support cloning
> range partitions from source table if there is any. For example, the
> following range partitions can't be cloned after execute 'create table
> custom_hash_range_single_clone like custom_hash_range_single.'
> {code:java}
> create table custom_hash_range_single (id int, c2 int, primary key(id, c2))
> partition by hash(id) partitions 3,
> range (c2)
> (
> partition 0 <= values < 10
> , partition 10 <= values < 20 hash partitions 2
> , partition 20 <= values < 30 hash(c2) partitions 3
> , partition 30 <= values < 40 hash(id) partitions 4
> , partition 40 <= values < 50 hash(id, c2) partitions 5
> )
> stored as kudu; {code}
> Consider supporting cloning range partitions in this jira.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
