You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2022/09/05 13:14:00 UTC
[jira] [Commented] (HADOOP-17961) s3 and abfs incremental listing: ask for a smaller first batch
[ https://issues.apache.org/jira/browse/HADOOP-17961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600397#comment-17600397 ]
Steve Loughran commented on HADOOP-17961:
-----------------------------------------
actually, the really slick way to do this is parse the XML responses through a SAX parser and so get the results incrementally, which we would be streamed direct to the iterators.
this would ensure the fewest #of requests (cost and efficiency), but deliver the lowest latencies possible between request issued and the first listing entries coming back
> s3 and abfs incremental listing: ask for a smaller first batch
> --------------------------------------------------------------
>
> Key: HADOOP-17961
> URL: https://issues.apache.org/jira/browse/HADOOP-17961
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure, fs/s3
> Affects Versions: 3.3.2
> Reporter: Steve Loughran
> Priority: Minor
>
> With code gradually adopting listStatusIncremental(), asking for a smaller initial batch could permit faster ramp of result processing.
> probably most significant on an s3 versioned bucket, as there the need to skip tombstones can result in significantly slower listings -but could benefit ABFS too
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org