You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Matteo Bertozzi (JIRA)" <ji...@apache.org> on 2016/08/26 16:58:20 UTC
[jira] [Updated] (HBASE-16507) Procedure v2 - Force DDL operation
to always roll forward
[ https://issues.apache.org/jira/browse/HBASE-16507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Bertozzi updated HBASE-16507:
------------------------------------
Attachment: HBASE-16507-v0.patch
> 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
>
>
> 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)