hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11674) oneByteBuf in CryptoInputStream and CryptoOutputStream should be non static
Date Thu, 05 Mar 2015 07:39:38 GMT

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

Yi Liu updated HADOOP-11674:
----------------------------
          Resolution: Fixed
       Fix Version/s: 2.7.0
    Target Version/s: 2.7.0  (was: 3.0.0, 2.7.0, 2.6.1)
        Hadoop Flags: Reviewed
              Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2. Thanks [~busbey] for the contribution.

> oneByteBuf in CryptoInputStream and CryptoOutputStream should be non static
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-11674
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11674
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 2.6.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 2.7.0
>
>         Attachments: HADOOP-11674.1.patch
>
>
> A common optimization in the io classes for Input/Output Streams is to save a single
length-1 byte array to use in single byte read/write calls.
> CryptoInputStream and CryptoOutputStream both attempt to follow this practice but mistakenly
mark the array as static. That means that only a single instance of each can be present in
a JVM safely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message