[ 
https://issues.apache.org/jira/browse/PHOENIX-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149683#comment-14149683
 ] 

James Taylor commented on PHOENIX-1296:
---------------------------------------

Let's start with the easy fix for this one as I mentioned above:  in the 
UngroupedAggregateRegionObserver, in your if statement that detects an analyze 
is being done, just always set the scan start/stop row to 
HConstant.EMPTY_START_ROW and HConstant.EMPTY_END_ROW. 

Then, for PHOENIX-1263, see my comment there.

> Scan entire region when tenant-specific table is analyzed
> ---------------------------------------------------------
>
>                 Key: PHOENIX-1296
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1296
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: Phoenix-1296_1.patch
>
>
> Based on the issue you've uncovered (that stats must be updated completely 
> for a region), there's a bit of follow on work needed if an ANALYZE is done 
> on a tenant-specific table. This case will be optimized to only scan and 
> analyze the current tenant's data, however we have to make sure that the 
> entire region(s) containing that tenant's data is scanned (or we'll end up 
> replacing the stats for that region with just the one we calculated for that 
> tenant).
> We should be able to do that based on ScanUtil.isAnalyzeTable(scan) being 
> true in DefaultParallelIteratorRegionSplitter and/or ParallelIterators.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to