Description
Now a table in kudu has an immutable HashBucketSchema once created. Sometimes we can't accurately predict the growth of data, after a period of time the number of hash buckets is too small for data of a time range.
Is it possible to support to alter the number of hash buckets for newly added range partitions? It seems has no effect on old data.
Attachments
Issue Links
- duplicates
-
KUDU-2671 Change hash number for range partitioning
- Resolved