[
https://issues.apache.org/jira/browse/HADOOP-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190251#comment-17190251
]
Steve Loughran commented on HADOOP-17242:
-----------------------------------------
this isn't actually a real bug as you never get a LIST to fail, only get, at
worse, an empty set of results. -and we
only get this mismatch on the first listing.
The patch will move all the block/reschedule logic into hasNext anyway, and add
some lower level tests of everything working
> S3A (async) ObjectListingIterator to block in hasNext() for results
> -------------------------------------------------------------------
>
> Key: HADOOP-17242
> URL: https://issues.apache.org/jira/browse/HADOOP-17242
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
>
> HADOOP-17074 made listing async in S3A, but the iterator's hasNext Call
> doesn't wait for the result. If invoked on an empty path it *may* return when
> it should be failing.
> Note: surfaced in code review, not seen in the wild and all our tests were
> happy
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
