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] [Commented] (PHOENIX-1263) Only cache guideposts on physical PTable
Date Fri, 26 Sep 2014 17:28:34 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149674#comment-14149674
] 

ramkrishna.s.vasudevan commented on PHOENIX-1263:
-------------------------------------------------

I tried different ways to do that to get a the physical table PName. But was not sure on that.


> 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)

Mime
View raw message