[
https://issues.apache.org/jira/browse/AVRO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379582#comment-15379582
]
ASF GitHub Bot commented on AVRO-607:
-------------------------------------
GitHub user dhalperi opened a pull request:
https://github.com/apache/incubator-beam/pull/664
Upgrade to Avro 1.8.1
This version has some important fixes for potential memory leaks.
(It does not have a fix for [AVRO-607] yet, but still has good fixes.)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dhalperi/incubator-beam avro-upgrade
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/664.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #664
----
commit 313a3e60042c86c0130c499ed5503380dab251cd
Author: Dan Halperin <[email protected]>
Date: 2016-07-15T15:43:35Z
Upgrade to Avro 1.8.1
This version has some important fixes for potential memory leaks.
(It does not have a fix for [AVRO-607] yet, but still has good fixes.)
----
> SpecificData.getSchema not thread-safe
> --------------------------------------
>
> Key: AVRO-607
> URL: https://issues.apache.org/jira/browse/AVRO-607
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.3.3, 1.8.1
> Reporter: Stephen Tu
> Fix For: 1.8.2
>
> Attachments: AVRO-607.patch
>
>
> SpecificData.getSchema uses a WeakHashMap to cache schemas, but WeakHashMap
> is not thread-safe, and the method itself is not synchronized. Seems like
> this could lead to the data structure getting corrupted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
