[
https://issues.apache.org/jira/browse/NIFI-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720243#comment-15720243
]
Mark Payne commented on NIFI-3071:
----------------------------------
I actually hit an ArrayIndexOutOfBoundsException on the ByteArrayOutputStream
the other day. It was in a unit test and was a corner case. However, it could
potentially affect any number of processors or the framework that use this
class. And as mentioned in NIFI-3073, it can be easy to accidentally depend on
these classes when intending to depend on the java counterpart. As a result,
this could be pretty dangerous. May be worth pushing for a release quickly
because of this ticket.
> Consider deprecating org.apache.nifi.stream.io.ByteArrayOutputStream in favor
> of jaba.io.ByteArrayOutputStream
> --------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3071
> URL: https://issues.apache.org/jira/browse/NIFI-3071
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Oleg Zhurakousky
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.1.1
>
>
> I believe the "efficiency" statements need to be revisited. For example,
> preliminary testing shows that there are no performance difference between
> using the one provided with java.io.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
