Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Thu, 21 Jul 2016 18:52:20 +0000 (UTC)
From: "Andrius Druzinis-Vitkus (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12470865.1280982502000.98767.1469127140909@Atlassian.JIRA>
In-Reply-To: <JIRA.12470865.1280982502000@Atlassian.JIRA>
References: <JIRA.12470865.1280982502000@Atlassian.JIRA> <JIRA.12470865.1280982502005@arcas>
Subject: [jira] [Issue Comment Deleted] (AVRO-607) SpecificData.getSchema
 not thread-safe
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 21 Jul 2016 18:52:23 -0000


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

Andrius Druzinis-Vitkus updated AVRO-607:
-----------------------------------------
    Comment: was deleted

(was: Hi [~busbey], thanks for that. I've just attempted to submit a patch. Added a brief release note but was surprised there wasn't a field for the actual patch! Apologies in advance for being a bit lost...)

> 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
>            Assignee: Andrius Druzinis-Vitkus
>            Priority: Blocker
>              Labels: newbie, patch
>             Fix For: 1.8.2
>
>         Attachments: AVRO-607.patch, 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)