You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/09/25 23:44:33 UTC
[jira] [Created] (PHOENIX-1296) Scan entire region when
tenant-specific table is analyzed
James Taylor created PHOENIX-1296:
-------------------------------------
Summary: 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
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)