You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2014/09/25 13:05:34 UTC
[jira] [Commented] (PHOENIX-1263) Only cache guideposts on physical
PTable
[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147624#comment-14147624 ]
ramkrishna.s.vasudevan commented on PHOENIX-1263:
-------------------------------------------------
[~giacomotaylor]
To do this I may need to read how the multi tenant tables are stored in the SYSTEM table and how the base multi-tenant table is accessed and how the tenant-specific tables are accessed.
> 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
>
> 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)