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

Chris Nauroth commented on HADOOP-12875:
----------------------------------------

[[email protected]], building on discussion in HADOOP-12666, our plan was to 
commit that and this together with known follow-on work to be tracked in 
separate JIRAs.  This would have broken the multi-month logjam on HADOOP-12666 
and allowed further progress to proceed more iteratively and easily.  The 
contract tests, while still needing the additional work you pointed out, are 
still going to be helpful for catching regressions during subsequent work.  Can 
I please ask you to compromise, lift your -1, and defer these additional items 
to be tracked in separate JIRAs?  If not, then would you at least consider 
deferring a subset of those items?

I had kicked off a pre-commit run right after committing HADOOP-12666.  
[~vishwajeet.dusane], the pre-commit warnings definitely need to be addressed, 
including the Findbugs warning.  Mysteriously, that Findbugs warning was not 
flagged during pre-commit of HADOOP-12666.

> [Azure Data Lake] Support for contract test and unit test cases
> ---------------------------------------------------------------
>
>                 Key: HADOOP-12875
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12875
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: fs, fs/azure, tools
>            Reporter: Vishwajeet Dusane
>            Assignee: Vishwajeet Dusane
>         Attachments: Hadoop-12875-001.patch, Hadoop-12875-002.patch, 
> Hadoop-12875-003.patch, Hadoop-12875-004.patch
>
>
> This JIRA describes contract test and unit test cases support for azure data 
> lake file system.



--
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