GitHub user holdenk opened a pull request:

    https://github.com/apache/spark/pull/11059

    [SPARK-13164][CORE][WIP] Replace deprecated synchronized buffer in core

    Building with scala 2.11 results in the warning trait SynchronizedBuffer in 
package mutable is deprecated: Synchronization via traits is deprecated as it 
is inherently unreliable. Consider java.util.concurrent.ConcurrentLinkedQueue 
as an alternative. Investigation shows we are already using 
ConcurrentLinkedQueue in other locations so switch our uses of 
SynchronizedBuffer to ConcurrentLinkedQueue.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/holdenk/spark 
SPARK-13164-replace-deprecated-synchronized-buffer-in-core

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/11059.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 #11059
    
----
commit 8d5b5b88dcecca993f2630794d29b058622f8d16
Author: Holden Karau <[email protected]>
Date:   2016-02-03T20:25:30Z

    Move ContextCleaner away from deprecated syncrhonized buffer API

commit 2904e4552bc5c2e1347e05c9c1b724aa02dbfd0c
Author: Holden Karau <[email protected]>
Date:   2016-02-03T20:28:31Z

    Move EventLoopSuite to ConcurrentLinkedQueue

commit 2ed2227092e4fff11b2f151cc6d880cf9d988436
Author: Holden Karau <[email protected]>
Date:   2016-02-03T20:48:25Z

    Convert more tests in core to use concurrentlinkedqueue

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to