[
https://issues.apache.org/jira/browse/PHOENIX-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090326#comment-14090326
]
Jeffrey Zhong commented on PHOENIX-1147:
----------------------------------------
{quote}
So it's a case where the parent table is in the cache, but the index table isn't
{quote}
That's correct. Finally I found the bug in the code as shown below. So we don’t
need to adjust the parentTable cache update. The latest changes in v4 patch.
{code}
.setSchemaName(schemaName).setTableName(tableName).build().buildException();
default:
try {
- // TODO: should we update the parent table by removing
the index?
- connection.removeTable(tenantId, tableName);
- } catch (TableNotFoundException ignore) { } // Ignore -
just means wasn't cached
-
+ connection.removeTable(tenantId,
SchemaUtil.getTableName(schemaName, tableName));
+ } catch (TableNotFoundException ignore) {}// Ignore - just
means wasn't cached
{code}
> Ensure data table is sent to client if index table changes states
> -----------------------------------------------------------------
>
> Key: PHOENIX-1147
> URL: https://issues.apache.org/jira/browse/PHOENIX-1147
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.0.0, 5.0.0
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Attachments: Phoenix-1147-v1.patch, Phoenix-1147-v2.patch,
> Phoenix-1147-v3.patch
>
>
> Add one test to cover RegionServer being killed while index is begin updated
> Add steps to make sure UPSERT & SELECT should still work after index is
> disabled.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
