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

ASF GitHub Bot logged work on HADOOP-16906:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Feb/21 06:52
            Start Date: 14/Feb/21 06:52
    Worklog Time Spent: 10m 
      Work Description: HeartSaVioR commented on pull request #2684:
URL: https://github.com/apache/hadoop/pull/2684#issuecomment-778737140


   Finally! Thanks again everyone!
   Just to double check, if I understand correctly, we are targetting this to 
3.3.1, right? This is merged to trunk but the JIRA issue is not resolved so not 
sure which target versions are.


----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 552305)
    Time Spent: 6h  (was: 5h 50m)

> Add some Abortable.abort() interface for streams etc which can be terminated
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-16906
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16906
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs, fs/azure, fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Assignee: Jungtaek Lim
>            Priority: Blocker
>              Labels: pull-request-available
>          Time Spent: 6h
>  Remaining Estimate: 0h
>
> Some IO we want to be able to abort rather than close cleanly, especially if 
> the inner stream is an HTTP connection which itself supports some abort() 
> method. For example: uploads to an object where we want to cancel the upload 
> without close() making an incomplete write visible.
> Proposed: Add a generic interface which things like streams can implement
> {code}
> AbortableIO {
>   public void abortIO() throws IOE;
> }
> {code}
> +do for s3a output stream. I wouldn't do this a passthrough on 
> FSDataOutputStream because we need to consider what expectations callers have 
> of an operation being "aborted"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to