[
https://issues.apache.org/jira/browse/HBASE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092545#comment-13092545
]
Ted Yu commented on HBASE-1730:
-------------------------------
Please rebase patch on latest TRUNK:
{code}
patching file src/main/ruby/shell.rb
Hunk #1 FAILED at 227.
1 out of 1 hunk FAILED -- saving rejects to file src/main/ruby/shell.rb.rej
patching file src/main/java/org/apache/hadoop/hbase/ipc/HMasterInterface.java
Hunk #1 FAILED at 26.
1 out of 2 hunks FAILED -- saving rejects to file
src/main/java/org/apache/hadoop/hbase/ipc/HMasterInterface.java.rej
{code}
> Near-instantaneous online schema and table state updates
> --------------------------------------------------------
>
> Key: HBASE-1730
> URL: https://issues.apache.org/jira/browse/HBASE-1730
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: stack
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: 1730-v2.patch, 1730-v3.patch, 1730.patch,
> HBASE-1730.patch
>
>
> We should not need to take a table offline to update HCD or HTD.
> One option for that is putting HTDs and HCDs up into ZK, with mirror on disk
> catalog tables to be used only for cold init scenarios, as discussed on IRC.
> In this scheme, regionservers hosting regions of a table would watch
> permanent nodes in ZK associated with that table for schema updates and take
> appropriate actions out of the watcher. In effect, schema updates become
> another item in the ToDo list.
> {{/hbase/tables/<table-name>/schema}}
> Must be associated with a write locking scheme also handled with ZK
> primitives to avoid situations where one concurrent update clobbers another.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
