You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Martin Kleppmann (JIRA)" <ji...@apache.org> on 2014/05/23 10:32:02 UTC
[jira] [Updated] (AVRO-1457) ReadOnly ByteBuffer serialization
state changes after writing
[ https://issues.apache.org/jira/browse/AVRO-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Kleppmann updated AVRO-1457:
-----------------------------------
Fix Version/s: 1.7.7
Status: Patch Available (was: Open)
I don't understand the intended semantics well enough to review this patch, but it sounds like something to include in 1.7.7. Marking as "patch available".
> 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)