[
https://issues.apache.org/jira/browse/KUDU-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565191#comment-17565191
]
ASF subversion and git services commented on KUDU-2671:
-------------------------------------------------------
Commit 23908bdbe753c25aa2a33796559ecf64f0197949 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=23908bdbe ]
KUDU-2671 fix consistency check in KuduScanner::NextBatch()
KuduScanner::Data::OpenTablet() can return earlier when the metacache
returns a tablet covering the partition key range past the partition key
provided. In such case, the 'proxy_' member of KuduScanner::Data isn't
set, and that's expected since the upper level code should continue with
the next tablet. The new test sub-scenarios introduced in [1] triggered
the consistency check on the 'data_->proxy_' member in
KuduScanner::NextBatch(), so this patch addresses the issue.
Also, this patch re-enables a few test sub-scenarios introduced in
[1] and [2].
[1]
https://github.com/apache/kudu/commit/b746978c71ce4a95b69d49c43d0ac852909a8b4e
[2]
https://github.com/apache/kudu/commit/1889d4c44385fec5efeeb2d287d9ab7a3544dcfe
Change-Id: Icfbdfac46f35d4d143f37845d158795bf1793da7
Reviewed-on: http://gerrit.cloudera.org:8080/18715
Reviewed-by: Khazar Mammadli <mammadli.kha...@cloudera.com>
Tested-by: Alexey Serbin <ale...@apache.org>
Reviewed-by: Mahesh Reddy <mre...@cloudera.com>
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
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.10#820010)
