[jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
[
https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-14606:
-
Fix Version/s: (was: 3.1.0)
Removing 3.1.0 fix-version from all JIRAs which are Invalid / Won't Fix /
Duplicate / Cannot Reproduce.
> S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward
> seek
> ---
>
> Key: HADOOP-14606
> URL: https://issues.apache.org/jira/browse/HADOOP-14606
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Steve Loughran
>Priority: Critical
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip bytes. Codepaths only seem to do this if read() returns -1, meaning end of
> stream is reached.
> If that happens when doing a forward seek via skip, then we have got our
> numbers wrong and are in trouble. Look for a negative response, log @ ERROR
> and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
[
https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated HADOOP-14606:
Target Version/s: 3.2.0 (was: 3.1.0)
> S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward
> seek
> ---
>
> Key: HADOOP-14606
> URL: https://issues.apache.org/jira/browse/HADOOP-14606
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Steve Loughran
>Priority: Critical
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip bytes. Codepaths only seem to do this if read() returns -1, meaning end of
> stream is reached.
> If that happens when doing a forward seek via skip, then we have got our
> numbers wrong and are in trouble. Look for a negative response, log @ ERROR
> and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
[
https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14606:
Priority: Critical (was: Major)
Target Version/s: 3.1.0
> S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward
> seek
> ---
>
> Key: HADOOP-14606
> URL: https://issues.apache.org/jira/browse/HADOOP-14606
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Steve Loughran
>Priority: Critical
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip bytes. Codepaths only seem to do this if read() returns -1, meaning end of
> stream is reached.
> If that happens when doing a forward seek via skip, then we have got our
> numbers wrong and are in trouble. Look for a negative response, log @ ERROR
> and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
[
https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14606:
Parent Issue: HADOOP-14831 (was: HADOOP-13204)
> S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward
> seek
> ---
>
> Key: HADOOP-14606
> URL: https://issues.apache.org/jira/browse/HADOOP-14606
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Steve Loughran
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip bytes. Codepaths only seem to do this if read() returns -1, meaning end of
> stream is reached.
> If that happens when doing a forward seek via skip, then we have got our
> numbers wrong and are in trouble. Look for a negative response, log @ ERROR
> and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
[
https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14606:
Summary: S3AInputStream: Handle http stream skip(n) skipping < n bytes in a
forward seek (was: S3AInputStream: Handle skip(n) skipping < n bytes in a
forward seek)
> S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward
> seek
> ---
>
> Key: HADOOP-14606
> URL: https://issues.apache.org/jira/browse/HADOOP-14606
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Steve Loughran
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip bytes. Codepaths only seem to do this if read() returns -1, meaning end of
> stream is reached. Wh
> If that happens when doing a forward seek via skip, then we have got our
> numbers wrong and are in trouble. Look for a negative response, log @ ERROR
> and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
[
https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14606:
Description:
There's some hints in the InputStream docs that {{skip(n)}} may skip S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward
> seek
> ---
>
> Key: HADOOP-14606
> URL: https://issues.apache.org/jira/browse/HADOOP-14606
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Steve Loughran
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip bytes. Codepaths only seem to do this if read() returns -1, meaning end of
> stream is reached.
> If that happens when doing a forward seek via skip, then we have got our
> numbers wrong and are in trouble. Look for a negative response, log @ ERROR
> and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
