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

Hudson commented on HBASE-16507:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #1632 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1632/])
HBASE-16507 Procedure v2 - Force DDL operation to always roll forward 
(matteo.bertozzi: rev 9c58d26d3bd5bd4e10be1084a24a62ed25722689)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/StateMachineProcedure.java


> Procedure v2 - Force DDL operation to always roll forward
> ---------------------------------------------------------
>
>                 Key: HBASE-16507
>                 URL: https://issues.apache.org/jira/browse/HBASE-16507
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, proc-v2
>    Affects Versions: 2.0.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16507-v0.patch, HBASE-16507-v1.patch
>
>
> Having rollback for DDLs was a bad idea. 
> and it turns out to be an unexpected behavior for the user. 
> DDLs only have transient errors (e.g. zk, hdfs, meta down)
> if we abort/rollback on a transient failure the user will get a failure,
> and it is not clear why the user needs to retry the command when the system 
> can do that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to