Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 14 May 2015 19:43:00 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12829338.1431465553000.117329.1431632580980@Atlassian.JIRA>
In-Reply-To: <JIRA.12829338.1431465553000@Atlassian.JIRA>
References: <JIRA.12829338.1431465553000@Atlassian.JIRA>
 <JIRA.12829338.1431465553909@arcas>
Subject: [jira] [Commented] (CASSANDRA-9366) make Functions.declared
 thread-safe
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tyler Hobbs commented on CASSANDRA-9366:
----------------------------------------

+1, with one minor nit that you can fix on commit: in {{Functions.declare()}}, move the variable assignment outside of the method call.

> make Functions.declared thread-safe
> -----------------------------------
>
>                 Key: CASSANDRA-9366
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9366
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>             Fix For: 2.2.x
>
>         Attachments: 9366.txt
>
>
> {{Functions.declared}} is an {{ArrayListMultimap}}, which is not thread safe.
> This wasn't a problem before UDFs. But with UDFs there can be concurrent reads & writes.
> Need to make it thread safe.


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