Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Table copy supports creating empty range partition
Currently when the source table's range partition is empty, using CLI command 'table copy xxx --create_table=true' to create the destination table, it will create a table with unbouned partition table. That is not right. Empty range partition is not equal to unbouned partition. For example: The source table is: TABLE test1 ( key INT32 NOT NULL, int_val INT32 NOT NULL, string_val STRING NULLABLE, PRIMARY KEY (key) ) HASH (key) PARTITIONS 2, RANGE (key) () OWNER root REPLICAS 1 COMMENT The destination table is: TABLE test1 ( key INT32 NOT NULL, int_val INT32 NOT NULL, string_val STRING NULLABLE, PRIMARY KEY (key) ) HASH (key) PARTITIONS 2, RANGE (key) ( PARTITION UNBOUNDED ) Change-Id: I59f62d7114772112b39f9fba0c5c90dd0a418a97 Reviewed-on: http://gerrit.cloudera.org:8080/21637 Reviewed-by: Yingchun Lai <[email protected]> Tested-by: Marton Greber <[email protected]> Reviewed-by: Marton Greber <[email protected]>
- Loading branch information