[
https://issues.apache.org/jira/browse/PHOENIX-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320132#comment-15320132
]
Ankit Singhal edited comment on PHOENIX-2949 at 6/8/16 6:50 AM:
----------------------------------------------------------------
Yes [~jamestaylor], it totally make sense to remove the limit of serial scan to
single region and give control to user to define the threshold for serial scan
as with stats we can achieve the parallelism within the region too.
But how about estimating parallel threshold bytes when guideposts are available
to
{code}
estimatedParallelThresholdBytes = 2 *
services.getProps().getLong(QueryServices.STATS_GUIDEPOST_WIDTH_BYTES_ATTRIB,
QueryServicesOptions.DEFAULT_STATS_GUIDEPOST_WIDTH_BYTES);
{code}
If it's ok, please review the attached patch.
was (Author: ankit.singhal):
Yes [~jamestaylor], it totally make sense to remove the limit of serial scan to
single region and give control to user to define the threshold for serial scan
as with stats we can achieve the parallelism within the region too.
But how about estimating parallel threshold bytes when guideposts are available
to
{code}
estimatedParallelThresholdBytes = 2 *
services.getProps().getLong(QueryServices.STATS_GUIDEPOST_WIDTH_BYTES_ATTRIB,
QueryServicesOptions.DEFAULT_STATS_GUIDEPOST_WIDTH_BYTES);
{code}
> Fix estimated region size when checking for serial query
> --------------------------------------------------------
>
> Key: PHOENIX-2949
> URL: https://issues.apache.org/jira/browse/PHOENIX-2949
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2949.patch, PHOENIX-2949_v1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
