You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/04/21 00:20:02 UTC

[jira] [Resolved] (PHOENIX-1892) Don't use alias in TableRef equality check if null

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

James Taylor resolved PHOENIX-1892.
-----------------------------------
    Resolution: Invalid

Thanks for the explanation, [~maryannxue]. Closing as invalid. This came up because MutationState is using TableRef as a key into a Map and with transactions we sometimes need to send only some of the pending updates to HBase (based on the TableRef from the query). We should really be using the physical table name instead.

> Don't use alias in TableRef equality check if null
> --------------------------------------------------
>
>                 Key: PHOENIX-1892
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1892
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>         Attachments: PHOENIX-1892.patch
>
>
> If either side of a TableRef has a null alias, it seems like the equality check shouldn't fail in this case.



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