[
https://issues.apache.org/jira/browse/HADOOP-13995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HADOOP-13995:
-----------------------------------
Attachment: HADOOP-13995-HADOOP-13345.003.patch
Definitely - I ran into that myself. I also removed my fix for the issue in
HADOOP-13877 now that was already fixed as a separate issue.
I now pass in S3 test paths so the endpoint is the same as the configured S3
bucket if nothing else is specified. I had to tweak some of the logic in
parseDynamoDBEndPoint to allow a metastore URL and s3 bucket to be passed in.
I'm not sure why that wouldn't be allowed - I think the logic now matches how
we actually end up deciding what to use. I'd appreciate it if [~eddyxu] could
take a quick look to make sure I'm not overlooking something important in the
original intentions.
> s3guard cli: make tests easier to run and address failure
> ---------------------------------------------------------
>
> Key: HADOOP-13995
> URL: https://issues.apache.org/jira/browse/HADOOP-13995
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Aaron Fabbri
> Assignee: Sean Mackrory
> Attachments: HADOOP-13995.001.patch, HADOOP-13995.002.patch,
> HADOOP-13995-HADOOP-13345.003.patch
>
>
> Following up on HADOOP-13650, we should:
> - Make it clearer which config parameters need to be set for test to succeed,
> and provide good defaults.
> - Address any remaining test failures.
> - Change TestS3GuardTool to an ITest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
