[
https://issues.apache.org/jira/browse/PHOENIX-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152887#comment-14152887
]
ramkrishna.s.vasudevan commented on PHOENIX-1263:
-------------------------------------------------
{code}
INFO] Reactor Summary:
[INFO]
[INFO] Apache Phoenix .................................... SUCCESS [1.541s]
[INFO] Phoenix Hadoop Compatibility ...................... SUCCESS [2.279s]
[INFO] Phoenix Hadoop2 Compatibility ..................... SUCCESS [2.200s]
[INFO] Phoenix Core ...................................... SUCCESS [16:51.552s]
[INFO] Phoenix - Flume ................................... SUCCESS [59.900s]
[INFO] Phoenix - Pig ..................................... SUCCESS [2:19.739s]
[INFO] Phoenix Assembly .................................. SUCCESS [25.681s]
[INFO] --------------------------------------------------------------------
{code}
All tests pass.
> 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)
