[
https://issues.apache.org/jira/browse/KUDU-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057715#comment-18057715
]
ASF subversion and git services commented on KUDU-2671:
-------------------------------------------------------
Commit 2856089dc61156b03c3cb204b84b1a2f7a503cbe in kudu's branch
refs/heads/branch-1.18.x from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=2856089dc ]
KUDU-3723 fix interpretation of new range partition specs
In the context of KUDU-2671, a new notation for specifying hash schema
of a range partition has been added. With the introduction of
range-specific hash schemas, the client side is free to send in
information on the newly added range partition as if it had a custom
hash schema, even if the new range's hash schema is the same as the
table-wide one. However, the system catalog should have normalized
the provided information, and stored the information on ranges with
the table-wide and custom hash schemas differently. The normalization
part was missing, and that was the reason for the reported issue.
This changelist addresses the problem and adds a new test scenario that
triggers an assertion without the fix.
Change-Id: Icceb138a919cd7afb572c6dd74695a3fcaaac99e
Reviewed-on: http://gerrit.cloudera.org:8080/23778
Tested-by: Alexey Serbin <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
(cherry picked from commit cad295f98a9eb2b390eb096d34e445fb27b8cca2)
Reviewed-on: http://gerrit.cloudera.org:8080/23960
Reviewed-by: Abhishek Chennaka <[email protected]>
> Change hash number for range partitioning
> -----------------------------------------
>
> Key: KUDU-2671
> URL: https://issues.apache.org/jira/browse/KUDU-2671
> Project: Kudu
> Issue Type: Improvement
> Components: client, java, master, server
> Affects Versions: 1.8.0
> Reporter: yangz
> Assignee: Mahesh Reddy
> Priority: Major
> Labels: feature, roadmap-candidate, scalability
> Fix For: 1.17.0
>
> Attachments: 屏幕快照 2019-01-24 下午12.03.41.png
>
>
> For our usage, the kudu schema design isn't flexible enough.
> We create our table for day range such as dt='20181112' as hive table.
> But our data size change a lot every day, for one day it will be 50G， but for
> some other day it will be 500G. For this case, it be hard to set the hash
> schema. If too big, for most case, it will be too wasteful. But too small,
> there is a performance problem in the case of a large amount of data.
>
> So we suggest a solution we can change the hash number by the history data of
> a table.
> for example
> # we create schema with one estimated value.
> # we collect the data size by day range
> # we create new day range partition by our collected day size.
> We use this feature for half a year, and it work well. We hope this feature
> will be useful for the community. Maybe the solution isn't so complete.
> Please help us make it better.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
