[
https://issues.apache.org/jira/browse/NIFI-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270202#comment-16270202
]
ASF GitHub Bot commented on NIFI-4628:
--------------------------------------
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/2300
@aburkard, thanks for contributing this PR, it looks very nice. I
appreciate that you maintained the existing default behavior while adding
forward-looking support. The code looks good. Thanks for adding the unit
test. The full build with contrib-check passes. ListS3 worked well in my
testing so far with both v1 and v2.
I have one suggestion. What would you think about re-phrasing the List
Type display options from the current `1` and `2` to something a bit more
verbose like `ListObjects v1` and `ListObjects v2`?
> Update ListS3 proccesor to support List Objects Version 2
> ---------------------------------------------------------
>
> Key: NIFI-4628
> URL: https://issues.apache.org/jira/browse/NIFI-4628
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Andrew Burkard
> Priority: Minor
>
> AWS has revised the List Objects API:
> http://docs.aws.amazon.com/AmazonS3/latest/API/v2-RESTBucketGET.html
> The main difference is the new API passes a continuation token in the
> response for multi-page listings rather than requiring the client to keep
> track of the lexicographically last key listed. The new version also appears
> to be the only API supported going forward for new AWS services (e.g.
> Snowball). It would be nice if the ListS3 processor supported either via an
> attribute.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
