hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7639) Enable online schema update by default
Date Fri, 09 Aug 2013 19:38:48 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735190#comment-13735190

Lars Hofhansl commented on HBASE-7639:

It's 172k of mostly new code, right? Agree it's risky. Still at least for us that would be
incredibly useful (we're doing a lot of coprocessor stuff with Phoenix, and each time we upgrade
the Phoenix coprocessor we need to restart the cluster at least with a rolling restart). It
would be much nicer if we could just online-update the tables.

I'll make a patch - if I get time - and put it up. Then we can decide on the risk. It's likely
that while I make the patch I'll find it too risky anyway.

> Enable online schema update by default 
> ---------------------------------------
>                 Key: HBASE-7639
>                 URL: https://issues.apache.org/jira/browse/HBASE-7639
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.95.2
>            Reporter: Enis Soztutar
>            Assignee: Elliott Clark
>             Fix For: 0.98.0, 0.95.2
>         Attachments: HBASE-7639-0.patch
> After we get HBASE-7305 and HBASE-7546, things will become stable enough to enable online
schema update to be enabled by default. 
> {code}
>   <property>
>     <name>hbase.online.schema.update.enable</name>
>     <value>false</value>
>     <description>
>     Set true to enable online schema changes.  This is an experimental feature.ยทยท
>     There are known issues modifying table schemas at the same time a region
>     split is happening so your table needs to be quiescent or else you have to
>     be running with splits disabled.
>     </description>
>   </property>
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message