hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4849) Idempotent create and append operations.
Date Tue, 18 Jun 2013 21:24:22 GMT

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

Suresh Srinivas commented on HDFS-4849:

bq. I intentionally worked on this patch to get it ready for 2.1 in advance, because the discussion
was concluded and everybody seemed to be in agreement.

I again think this jira, which is an improvement, does not qualify as 2.1.0-beta blocker.
The patch attached came on 11th of June. There is no need to block the release for this change;
especially considering this can be done without breaking compatibility. As regards working
on content to included in the next release, you had no qualms about arguing for excluding
some of the features that was being developed for more than 7-8 months from a planned 2.x
release stream. Not sure why the current release, for which we already had discussion about
what feature set to be included, should be blocked for a content that was not brought up earlier.
> Idempotent create and append operations.
> ----------------------------------------
>                 Key: HDFS-4849
>                 URL: https://issues.apache.org/jira/browse/HDFS-4849
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.0.4-alpha
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>            Priority: Blocker
>         Attachments: idempotentCreate.patch, idempotentCreate.patch, idempotentCreate.patch
> create, append and delete operations can be made idempotent. This will reduce chances
for a job or other app failures when NN fails over.

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