avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1457) ReadOnly ByteBuffer serialization state changes after writing
Date Wed, 28 May 2014 22:07:03 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011680#comment-14011680
] 

Hudson commented on AVRO-1457:
------------------------------

FAILURE: Integrated in AvroJava #452 (See [https://builds.apache.org/job/AvroJava/452/])
AVRO-1457. Java: Fix Encoder so that offset in non-array-backed ByteBuffers is not altered
when written. Contributed by Rob Turner. (cutting: rev 1598146)
* /avro/trunk/CHANGES.txt
* /avro/trunk/lang/java/avro/src/main/java/org/apache/avro/io/Encoder.java
* /avro/trunk/lang/java/avro/src/main/java/org/apache/avro/io/JsonEncoder.java
* /avro/trunk/lang/java/avro/src/test/java/org/apache/avro/io/TestBinaryEncoderFidelity.java


> ReadOnly ByteBuffer serialization state changes after writing
> -------------------------------------------------------------
>
>                 Key: AVRO-1457
>                 URL: https://issues.apache.org/jira/browse/AVRO-1457
>             Project: Avro
>          Issue Type: Bug
>    Affects Versions: 1.7.4
>            Reporter: GregWhitsitt
>            Assignee: Rob Turner
>             Fix For: 1.7.7
>
>         Attachments: AVRO-1457.patch, ByteBufferTest.java, test.avdl
>
>
> Using the GenericDatumWriter specifically, writing out an avro containing a read-only
ByteBuffer changes state of the original object, making it unusable after the initial write.
 Potentially either the ByteBuffer needs to be copied prior to writing if read-only, or the
offset needs to be reset after writing.  
> I'll attach a simple test which shows the issue  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message