phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1263) Only cache guideposts on physical PTable
Date Tue, 30 Sep 2014 08:46:34 GMT


ramkrishna.s.vasudevan commented on PHOENIX-1263:

I made a change in the ParallelIterators for this case TenantSpecificViewIndexCompileTest.
It was failing as the physical table was actually not present in the cache also.  The change
that you have suggested also results in TableNotFoundException.
Infact in the test case TenantSpecificViewIndexCompileTest the tenantId is not null so if
we want to ensure we get the IDX_T table whole ref name is I1 we need to pass the tenant id
and it should not be null.

> Only cache guideposts on physical PTable
> ----------------------------------------
>                 Key: PHOENIX-1263
>                 URL:
>             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
> 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

View raw message