[
https://issues.apache.org/jira/browse/PHOENIX-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201709#comment-14201709
]
James Taylor commented on PHOENIX-1408:
---------------------------------------
Thanks, [~apurtell]. Any opinion on what we should do in Phoenix? Do you think
it makes sense to remove our calls to disable the table before modifying it and
doc that the change will take place asynchronously? We could fix our unit tests
easily enough.
> 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
>
> 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)
