[ https://issues.apache.org/jira/browse/KUDU-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541032#comment-17541032 ]
ASF subversion and git services commented on KUDU-2671: ------------------------------------------------------- Commit ce499cec329874db03317ad57a165959fb8893b4 in kudu's branch refs/heads/master from Alexey Serbin [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=ce499cec3 ] KUDU-2671 fix the check for hash dimensions uniformity Before this patch, it was possible to create a table without ranges using the table-wide hash schema and ranges with custom hash schemas even if the table-wide hash schema had number of hash dimensions different from per-range custom hash schemas. This patch fixes the bug. I added a corresponding test scenario, updated existing ones, and removed a duplicate one. This is a follow-up to 6998193e69eeda497f912d1d806470c95b591ad4. Change-Id: I8c1282973deba57269f6e962be77e27baa39b187 Reviewed-on: http://gerrit.cloudera.org:8080/18532 Reviewed-by: Mahesh Reddy <mre...@cloudera.com> Tested-by: Alexey Serbin <ale...@apache.org> Reviewed-by: Attila Bukor <abu...@apache.org> > 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 > 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.7#820007)