You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/02/05 11:12:40 UTC
[jira] [Commented] (SPARK-13204) Replace use of
mutable.SynchronizedMap with ConcurrentHashMap
[ https://issues.apache.org/jira/browse/SPARK-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133940#comment-15133940 ]
Sean Owen commented on SPARK-13204:
-----------------------------------
I think you have been around long enough to know that you need to set JIRA fields correctly if you're going to open one. This can't be a 'major bug' and has no component. We also just fixed this right? It's a duplicate
> Replace use of mutable.SynchronizedMap with ConcurrentHashMap
> -------------------------------------------------------------
>
> Key: SPARK-13204
> URL: https://issues.apache.org/jira/browse/SPARK-13204
> Project: Spark
> Issue Type: Bug
> Reporter: Ted Yu
>
> From http://www.scala-lang.org/api/2.11.1/index.html#scala.collection.mutable.SynchronizedMap :
> Synchronization via traits is deprecated as it is inherently unreliable. Consider java.util.concurrent.ConcurrentHashMap as an alternative.
> This issue is to replace the use of mutable.SynchronizedMap and add scalastyle rule banning mutable.SynchronizedMap
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org