avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1457) ReadOnly ByteBuffer serialization state changes after writing
Date Sat, 24 May 2014 21:27:01 GMT

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

Rob Turner commented on AVRO-1457:
----------------------------------

I cannot commit this at the moment due to password problems. Thanks Doug for the offer to
do this for me.

> 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