[
https://issues.apache.org/jira/browse/PHOENIX-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225705#comment-14225705
]
Hudson commented on PHOENIX-1408:
---------------------------------
SUCCESS: Integrated in Phoenix-master #501 (See
[https://builds.apache.org/job/Phoenix-master/501/])
PHOENIX-1408 Don't disable table before modifying HTable metadata (Samarth
Jain) (jtaylor: rev 152f98fe71d494e9a80cb619dfd7170a85dc5ffe)
* phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/AlterTableIT.java
*
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
> Don't disable table before modifying HTable metadata
> ----------------------------------------------------
>
> Key: PHOENIX-1408
> URL: https://issues.apache.org/jira/browse/PHOENIX-1408
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Samarth Jain
> Attachments: PHOENIX-1408.patch, PHOENIX-1408_v2.patch,
> PHOENIX-1408_v3.patch
>
>
> In 0.98, HBase supports modifying the HTable metadata without disabling the
> table first. We should remove our calls to htable.disableTable() and
> htable.enableTable() in ConnectionQueryServicesImpl when we modify the table
> metadata. The only time we still need to disable the table is before we drop
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
