[
https://issues.apache.org/jira/browse/KUDU-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555730#comment-17555730
]
ASF subversion and git services commented on KUDU-2671:
-------------------------------------------------------
Commit 45a7857b494703ef5cf9da8671c75da88d5fc16d in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=45a7857b4 ]
[rpc] report the names of the unsupported feature flags
While introducing feature flags in the scope of KUDU-2671, I noticed
that missing feature flags are not reported in the error messages
(at least, I was looking at master_proxy_rpc.cc). This patch addresses
that, making corresponding error messages more actionable.
As for test coverage, I updated a couple of test scenarios in
dynamic_multi_master-test.cc to provide initial coverage.
In addition, a follow-up patch will add a new test scenario into
flex_partitioning_client-test.cc.
Change-Id: Id9805dc3fb4ba0a734ca92198bc5dc6449f588b7
Reviewed-on: http://gerrit.cloudera.org:8080/18631
Tested-by: Kudu Jenkins
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)
