[ https://issues.apache.org/jira/browse/KUDU-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402346#comment-17402346 ]
ASF subversion and git services commented on KUDU-2671: ------------------------------------------------------- Commit 888f42a7760377c21237643a0c2396870663f79c in kudu's branch refs/heads/master from Alexey Serbin [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=888f42a ] [tablet] small clean-up While making changes in TabletMetadata's code related to KUDU-2671, I found it's possible to improve the code around: * LogPrefix() now returns const reference instead of copy of a string * TabletMetadata's destructor can be trivial * TabletBootstrap::SetStatusMessage() uses move semantics This changelist does not contain any significant functional changes. Change-Id: I8ebe39d483605840b22e6ec2d9eb66b1f4fe9b07 Reviewed-on: http://gerrit.cloudera.org:8080/17797 Reviewed-by: Bankim Bhavsar <ban...@cloudera.com> Tested-by: Kudu Jenkins > 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.3.4#803005)