[
https://issues.apache.org/jira/browse/HADOOP-12635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dushyanth updated HADOOP-12635:
-------------------------------
Attachment: HADOOP-12635.003.patch
[~cnauroth] The conditions for the update of blob metadata in Append depends on
the following conditions:
1) If append lease metadata is not part of the Blob. In this case this is the
first client to Append so we update the metadata.
2) If append lease metadata is present and timeout has occurred. In this case
irrespective of what the value of the append lease is we update the metadata.
3) If append lease metadata is present and is equal to testCondition value
(passed as parameter) and timeout has not occurred, we update the metadata.
4) If append lease metadata is present and is not equal to testCondition value
(passed as parameter) and timeout has not occurred, we do not update metadata
and return false.
The updatePossible flag enforces these conditions. But you are correct in that
it is difficult to understand and thus maintain. I have made the change to
follow the check you have suggested and added comments to specify the condition
explicitly. Adding Patch v003 .
Testing same as Patch v002.
> Adding Append API support for WASB
> ----------------------------------
>
> Key: HADOOP-12635
> URL: https://issues.apache.org/jira/browse/HADOOP-12635
> Project: Hadoop Common
> Issue Type: Improvement
> Components: azure
> Affects Versions: 2.7.1
> Reporter: Dushyanth
> Assignee: Dushyanth
> Attachments: Append API.docx, HADOOP-12635.001.patch,
> HADOOP-12635.002.patch, HADOOP-12635.003.patch
>
>
> Currently the WASB implementation of the HDFS interface does not support
> Append API. This JIRA is added to design and implement the Append API support
> to WASB. The intended support for Append would only support a single writer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
