[
https://issues.apache.org/jira/browse/HADOOP-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122184#comment-16122184
]
Steve Loughran commented on HADOOP-14749:
-----------------------------------------
thx, I'll go through Mingliang's comments and do a final revision.
* yes. should use DynamoDB everywhere.
* we do generate javadocs, though I'm not sure the publishing is code. So I'm
trying to be consistent.
* provision burden? You mean allow us to overspecify for peak loads. Makes sense
BTW, one situation I'm thinking about now: how to handle s3guard as a read-only
client. That is, you can get the auth/hon-auth data from others, but you can't
write back yourself (indeed, can't write back to the FS)
> review s3guard docs & code prior to merge
> -----------------------------------------
>
> Key: HADOOP-14749
> URL: https://issues.apache.org/jira/browse/HADOOP-14749
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation, fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-14749-HADOOP-13345-001.patch,
> HADOOP-14749-HADOOP-13345-002.patch, HADOOP-14749-HADOOP-13345-003.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Pre-merge cleanup while it's still easy to do
> * Read through all the docs, tune
> * Diff the trunk/branch files to see if we can reduce the delta (and hence
> the changes)
> * Review the new tests
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
