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

John Zhuge edited comment on HADOOP-13929 at 1/27/17 6:56 AM:
--------------------------------------------------------------

>From hadoop-aws/index.md, {{test.fs.s3a.name}} is for integration tests, while 
>{{fs.contract.test.fs.s3a}} is for filesystem contract tests. Should ADLS also 
>use 2 properties to differentiate these 2 types of tests in {{live}} directory?

BTW, is hadoop-aws/index.md accurate about the use of 
{{contract-test-options.xml}}?


was (Author: jzhuge):
>From hadoop-aws/index.md, {{test.fs.s3a.name}} is for integration tests, while 
>{{fs.contract.test.fs.s3a}} is for filesystem contract tests. Should think 
>ADLS differentiate these 2 types of tests?

BTW, is hadoop-aws/index.md accurate about the use of 
{{contract-test-options.xml}}?

> ADLS connector should not check in contract-test-options.xml
> ------------------------------------------------------------
>
>                 Key: HADOOP-13929
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13929
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/adl, test
>    Affects Versions: 3.0.0-alpha2
>            Reporter: John Zhuge
>            Assignee: John Zhuge
>             Fix For: 3.0.0-alpha3
>
>         Attachments: HADOOP-13929.001.patch, HADOOP-13929.002.patch, 
> HADOOP-13929.003.patch, HADOOP-13929.004.patch, HADOOP-13929.005.patch, 
> HADOOP-13929.006.patch, HADOOP-13929.007.patch, HADOOP-13929.008.patch, 
> HADOOP-13929.009.patch
>
>
> Should not check in the file {{contract-test-options.xml}}. Make sure the 
> file is excluded by {{.gitignore}}. Make sure ADLS {{index.md}} provides a 
> complete example of this file.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to