phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1296) Scan entire region when tenant-specific table is analyzed
Date Fri, 26 Sep 2014 12:18:34 GMT


ramkrishna.s.vasudevan commented on PHOENIX-1296:

I don't think this we have to do. Consider there are two tenants that has the Tenant ID as
AZ and SZ (for example).
Assume in the tenantID1 there is an entry row1.
Now when the guideposts are formed for tenantID1 then the start row will anyway have AZ to
The guideposts will select [*][AZ], [AZ][AZrow1],[AZrow1][*].
This seems like we are scanning the entire region but as the start row is anyway AZ to AZ1
our scan would anyway get restricted within that range.  Do you feel we still need this?

> Scan entire region when tenant-specific table is analyzed
> ---------------------------------------------------------
>                 Key: PHOENIX-1296
>                 URL:
>             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

View raw message