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/10/01 09:03:33 UTC
[jira] [Resolved] (PHOENIX-1263) Only cache guideposts on physical
PTable
[ https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ramkrishna.s.vasudevan resolved PHOENIX-1263.
---------------------------------------------
Resolution: Fixed
Fix Version/s: 3.2
4.2
Pushed to 3.0, 4.0 and master. Thanks for all the reviews and feedback [~jamestaylor]
> 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
> Fix For: 4.2, 3.2
>
> Attachments: Phoenix-1263_1.patch, Phoenix-1263_6.patch, Phoenix-1263_7.patch, Phoenix-1263_7_3.0.patch, Phoenix-1263_8.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)