beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-318) AvroCoder may be vulnerable to AVRO-607
Date Thu, 02 Jun 2016 19:42:59 GMT

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

Daniel Halperin updated BEAM-318:
---------------------------------
    Description: 
See AVRO-607

The hypothesis is that even though AvroCoder is threadsafe according to Avro's javadoc, an
underlying bug in Avro library makes thread-unsafe access to a Java WeakHashMap. However I
have not yet succeeded at reproducing the bug; with some failed attempts in the linked GitHub
Pull Request history.


  was:
See AVRO-607

The hypothesis is that even though AvroCoder is threadsafe according to Avro's javadoc, an
underlying bug in AvroCoder makes thread-unsafe access to a Java WeakHashMap. However I have
not yet succeeded at reproducing the bug; with some failed attempts in the linked GitHub Pull
Request history.



> AvroCoder may be vulnerable to AVRO-607
> ---------------------------------------
>
>                 Key: BEAM-318
>                 URL: https://issues.apache.org/jira/browse/BEAM-318
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>
> See AVRO-607
> The hypothesis is that even though AvroCoder is threadsafe according to Avro's javadoc,
an underlying bug in Avro library makes thread-unsafe access to a Java WeakHashMap. However
I have not yet succeeded at reproducing the bug; with some failed attempts in the linked GitHub
Pull Request history.



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

Mime
View raw message