[
https://issues.apache.org/jira/browse/PHOENIX-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156196#comment-15156196
]
Lars Hofhansl commented on PHOENIX-1701:
----------------------------------------
Load based would be awesome! In theory all the information is there in HBase
(RegionLoad and friends).
The code to get scans from guideposts is in
BaseResultIterators.getParallelScans(...), right? Would that be only place to
change to combine guideposts?
> Adapt guidepost selection at compile time
> -----------------------------------------
>
> Key: PHOENIX-1701
> URL: https://issues.apache.org/jira/browse/PHOENIX-1701
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lars Hofhansl
>
> Currently we tweak the guide post width for the partition size we want - for
> example it just changed to 100mb to 300mb because FAST_DIFF is used by
> default.
> Instead it might better to collect more guideposts (maybe even as low as
> every 10mb) and then combine them at compile time into larger chunks.
> If we store them correctly the adjacent guideposts would be stored in order
> in the stats table and hence we would scan that table until we have a size we
> want (in terms of chunk size).
> The more information we have, the better, we can combine smaller guideposts,
> but we cannot split larger ones because we lack information.
> Just filing as a brainstorming issue for debate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
