[
https://issues.apache.org/jira/browse/PHOENIX-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921779#comment-13921779
]
Hudson commented on PHOENIX-102:
--------------------------------
FAILURE: Integrated in Apache Phoenix - Branch:4.0 #35 (See
[https://builds.apache.org/job/Phoenix-4.0/35/])
PHOENIX-102 IndexMaintainer constructor doesn't set isMultiTenant correctly
(JamesTaylor) (jamestaylor: rev 1190a54b252763b9373defa556f82b832cc87508)
* phoenix-core/src/main/java/org/apache/phoenix/schema/PTableImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/index/IndexMaintainer.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/PNameFactory.java
> IndexMaintainer constructor doesn't set isMultiTenant correctly
> ---------------------------------------------------------------
>
> Key: PHOENIX-102
> URL: https://issues.apache.org/jira/browse/PHOENIX-102
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Attachments: patch.diff
>
>
> Currently IndexMaintainer is using
> {code}
> PName tenantId = dataTable.getTenantId();
> this.isMultiTenant = tenantId != null
> {code}
> The check "tenantId != null" doesn't cover the case tenantId could be empty
> pname value. In addition, dataTable.isMultiTenant has already exposed right
> value so we should use dataTable.isMultiTenant() instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
