phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-1296) Scan entire region when tenant-specific table is analyzed
Date Sat, 27 Sep 2014 06:47:34 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ramkrishna.s.vasudevan updated PHOENIX-1296:
--------------------------------------------
    Attachment: Phoenix-1296_3.patch

As per the discussion just attaching the patch that would make the tenant specific tables
to scan entire region so that we could store guideposts against the physical table.

> 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, Phoenix-1296_3.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)

Mime
View raw message