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

ASF GitHub Bot commented on HADOOP-19189:
-----------------------------------------

steveloughran opened a new pull request, #6857:
URL: https://github.com/apache/hadoop/pull/6857

   
   * parameterize the test run rather than do it from within the test suite.
   * log what the committer factory is up to (and improve its logging)
   * close all filesystems, then create the test filesystem with cache enabled.
   
   The cache is critical, we want the fs from cache to be used when querying 
filesystem properties, rather than one created from the committer jobconf, 
which will have the same options as the task committer, so not actually 
validate the override logic.
   
   The tests were therefore failing correctly, because the test environment 
wasn't being set up.
   
   I have no idea why this worked before.
   
   
   ### How was this patch tested?
   
   Reworked ITestS3ACommitterFactory tested against s3 london.
   
   rerunning full -Dscale test to make sure that none of the changes i made to 
the production code have problems
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [X] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> ITestS3ACommitterFactory failing
> --------------------------------
>
>                 Key: HADOOP-19189
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19189
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.4.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> we've had ITestS3ACommitterFactory failing for a while, where it looks like 
> changed committer settings aren't being picked up.
> {code}
> ERROR] 
> ITestS3ACommitterFactory.testEverything:115->testInvalidFileBinding:165 
> Expected a org.apache.hadoop.fs.s3a.commit.PathCommitException to be thrown, 
> but got the result: : 
> FileOutputCommitter{PathOutputCommitter{context=TaskAttemptContextImpl{JobContextImpl
> {code}
> I've spent some time looking at it and it is happening because the test sets 
> the fileystem ref for the local test fs, and not that of the filesystem 
> created by the committer, which is where the option is picked up.
> i've tried to parameterize it but things are still playing up and I'm not 
> sure how hard to try to fix.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to