[ https://issues.apache.org/jira/browse/HADOOP-16906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran reassigned HADOOP-16906: --------------------------------------- Assignee: Jungtaek Lim > 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: 2h > 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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org