[
https://issues.apache.org/jira/browse/HADOOP-12635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095376#comment-15095376
]
Chris Nauroth commented on HADOOP-12635:
----------------------------------------
[~dchickabasapa], {{TestNativeAzureFileSystemAppend}} extends
{{NativeAzureFileSystemTestBase}}. If you look at the {{setUp}} method in the
base class, it already takes care of skipping the tests if not running against
the live service. I think the problem is that
{{TestNativeAzureFileSystemAppend}} overrides {{setUp}} but never calls back up
to {{super.setUp()}} to trigger this logic.
In your next patch revision, I recommend removing the {{setUp}} and
{{tearDown}} methods from {{TestNativeAzureFileSystemAppend}}. I think the
base class implementation does everything you need. The {{FileSystem}}
instance is exposed in the base class as a protected member named {{fs}}, so
you can refer to that in your test cases. I don't think you need to track the
{{FileSystem}} or the {{AzureBlobStorageTestAccount}} in members of the
subclass.
> 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-004.patch,
> 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)
