[jira] [Resolved] (PHOENIX-1897) Use physical table name as key in top level map for MutationState

["James Taylor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor resolved PHOENIX-1897.
-----------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 4.8.0)

This work will be done as part of PHOENIX-2028

> Use physical table name as key in top level map for MutationState
> -----------------------------------------------------------------
>
>                 Key: PHOENIX-1897
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1897
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>
> We're currently using TableRef as the key for the top level map in MutationState for uncommitted data. With the addition of transactions, there are times we pass a TableRef from a SELECT statement which may have an alias. This forces us to work around this for the equality checks by creating a new TableRef with a null alias.
> We really should be using the physical table name as a key instead. Updates to views would naturally fold into the same set of updates which is what we want. Also, for indexes, we should map back to the physical table name through the following logic:
> - for global indexes: get the parent table name
> - for local or shared indexes, get the physical table name and extract the physical table name from the name
> - for views, get the physical table name
> - for tables, get the physical table name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)