phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1408) Don't disable table before modifying HTable metadata
Date Thu, 20 Nov 2014 18:38:34 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219747#comment-14219747
] 

Samarth Jain commented on PHOENIX-1408:
---------------------------------------

Thanks for the review [~jamestaylor]. If I remember correctly, we want the timeout fix in
ParallelIterators as part of our next patch release 4.2.2. I am guessing we probably want
this new feature for 4.3 which means the exception code won't be there in 4.2.2.  If you would
like, I could update my patch for PHOENIX-1463 with this new exception code.

> 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
>
>
> 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)

Mime
View raw message