[
https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152975#comment-14152975
]
ramkrishna.s.vasudevan commented on PHOENIX-1263:
-------------------------------------------------
For the start and stop row also for now we are not collecting the guide posts
just using the region boundaries. So using them and setting the start and stop
row to empty[] is fine as the region is going to be a full region scan.
Incase we are planning to change the logic in the DefaultIterators to use the
guideposts then if we do it in the preScannerOpen then there is a chance that
we will end up doing full region scan instead of using the guide posts.
> Only cache guideposts on physical PTable
> ----------------------------------------
>
> Key: PHOENIX-1263
> URL: https://issues.apache.org/jira/browse/PHOENIX-1263
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: ramkrishna.s.vasudevan
> Attachments: Phoenix-1263_1.patch, Phoenix-1263_6.patch
>
>
> Rather than caching the guideposts on all tenant-specific tables, we should
> cache them only on the physical table. On the client side, we should also
> update the cache with the latest for the base multi-tenant table when we
> update the cache for a tenant-specific table. Then when we lookup the
> guideposts, we should ensure that we're getting them from the physical table.
> Otherwise, it'll be difficult to keep the guideposts cached on the PTable in
> sync across all tenant-specific tables (not to mention using quite a bit of
> memory).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
