hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Marquardt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14680) Azure: IndexOutOfBoundsException in BlockBlobInputStream
Date Tue, 25 Jul 2017 19:56:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Marquardt updated HADOOP-14680:
    Attachment: HADOOP-14680-001.patch

Attaching HADOOP-14680-001.patch.  

This fixes the issure where {{MemoryOutputStream.capacity()}} returns the wrong value.  The
function was supposed to return the total capacity of the stream and it now does that.

A new test case was added.  The new test case fails without the fix.

> Azure: IndexOutOfBoundsException in BlockBlobInputStream
> --------------------------------------------------------
>                 Key: HADOOP-14680
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14680
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/azure
>            Reporter: Rajesh Balamohan
>            Priority: Minor
>         Attachments: HADOOP-14680-001.patch
> https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/BlockBlobInputStream.java#L361
> On certain conditions, BlockBlobInputStream can throw IndexOutOfBoundsException. Following
is an example
> {{length:297898, offset:4194304, buf.len:4492202, writePos:4194304}} : 
> In this case, {{MemoryOutputStream::capacity()}} would end up returning negative value
and can cause {{IndexOutOfBoundsException}}
> It should be {{return buffer.length - offset;}} to determine current capacity.

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