[ https://issues.apache.org/jira/browse/ASTERIXDB-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845305#comment-17845305 ]
ASF subversion and git services commented on ASTERIXDB-3368: ------------------------------------------------------------ Commit f30653bcb1c3f125d4d097c91556c466cdb3e9c0 in asterixdb's branch refs/heads/master from Murtadha Makki Al Hubail [ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=f30653bcb1 ] [ASTERIXDB-3368][EXT] Abort S3 streams before closing - user model changes: no - storage format changes: no - interface changes: no Details: - Abort the S3 stream to avoid fully consuming the stream in cases where we would like to close the stream early. Change-Id: I5e85ab19734f417e6a38b522db5298534951687e Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18207 Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: Michael Blow <mb...@apache.org> Integration-Tests: Michael Blow <mb...@apache.org> > Closing S3 streams early still reads the file to the end > -------------------------------------------------------- > > Key: ASTERIXDB-3368 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-3368 > Project: Apache AsterixDB > Issue Type: Bug > Components: EXT - External data > Affects Versions: 0.9.9 > Reporter: Murtadha Makki Al Hubail > Assignee: Murtadha Makki Al Hubail > Priority: Major > Labels: triaged > Fix For: 0.9.9 > > > When an S3 file stream is closed early (e.g., due to a limit query), the > stream is still being read until the end. We should abort the stream to > indicate that we shouldn't be read to the end. -- This message was sent by Atlassian Jira (v8.20.10#820010)