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

Steve Loughran commented on HADOOP-13589:
-----------------------------------------

now we've got multiple back ends (and dynamo soon), life is complex. I'd like 
to have the option to mandate s3guard, which if set goes to local 
(authoritative = ? ), but allow us to switch to dynamodb as well.

{{S3ATestUtils.getTestProperty()}} will grab a property for a test, giving a 
sysprop which != "unset" the ability to override anything in the XML test 
configurations. This would let you 

# have a property {{-Ds3guard}}
# which will enable an {{s3guard}} profile to set what we want

if we modify the surefire/failsafe profiles to pass down a set of system 
properties, which are all set to {{unset}} by default then any of those set in 
the s3guard profile, or set on the maven command line will be picked up and 
override any in the XML files. 

The other thing to consider is junit profiles. HADOOP-13834 covers that idea as 
a way of enabling scale tests, rather than the contrived bits in 
{{AbstractS3aScaleTests}}. I haven't got that working, and haven't really put 
in the time to understand why —it felt like one of those interesting wastes of 
large amounts of time. A thought though. 





> S3Guard: Allow execution of all S3A integration tests with S3Guard enabled.
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-13589
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13589
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Assignee: Steve Loughran
>
> With S3Guard enabled, S3A must continue to be functionally correct.  The best 
> way to verify this is to execute our existing S3A integration tests in a mode 
> with S3A enabled.



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