hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HADOOP-17242) S3A (async) ObjectListingIterator to block in hasNext() for results
Date Tue, 08 Sep 2020 14:02:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-17242?focusedWorklogId=480152&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-480152

ASF GitHub Bot logged work on HADOOP-17242:

                Author: ASF GitHub Bot
            Created on: 08/Sep/20 14:01
            Start Date: 08/Sep/20 14:01
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on pull request #2273:
URL: https://github.com/apache/hadoop/pull/2273#issuecomment-688895798

   on this again. Need to think about what happens after hasNext raises an exception. IMO
we should cache it and rethrow on all subsequent hasNext/next. Without that if you catch an
IOE and call hasNext again it may get confused (maybe, I'd need to experiment)

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 480152)
    Time Spent: 1h 10m  (was: 1h)

> 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: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message