[SPARK-13175] Cleanup deprecation warnings from Scala 2.11 upgrade

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Done
• Fix Version/s: 2.0.0
• Component/s: DStreams, Examples, Spark Core, SQL
• Assignee: Holden Karau
• Reporter: Holden Karau
• Created: 04/Feb/16 00:01
• Updated: 16/Mar/16 09:40
• Resolved: 16/Mar/16 09:40

Description

We should cleanup whatever deprecation warnings we can now that the build defaults to 2.11 - some of them are important (e.g. old behaviour was unreliable) and others just distract from finding the important ones in our build. We should try and fix both. This can be thought of as the follow up to https://issues.apache.org/jira/browse/SPARK-721 where we fixed a bunch of the warnings back in the day.

Sub-Tasks

• Stop using RichException.getStackTrace it is deprecated: Resolved
• Update promise & future to Promise and Future as the old ones are deprecated: Resolved
• Investigate replacing SynchronizedQueue as it is deprecated: Resolved
• Ignore deprecation warning for ProcessBuilder lines_!: Resolved
• Update ActorWordCount example to not directly use low level linked list as it is deprecated.: Resolved
• Migrate away from SynchronizedMap which is deprecated: Resolved
• Replace Pair with tuples: Resolved
• Investigate math.round on integer number in MFDataGenerator.scala:109: Resolved
• Make a private non-deprecated version of setRuns: Resolved
• Silence or skip unsafe deprecation warnings: Resolved
• Stop using our internal deprecated .metrics on ExceptionFailure instead use accumUpdates: Resolved
• Cleanup transient annotations which aren't being applied: Resolved
• Move away from deprecated ThreadPoolTaskSupport: Resolved
• Stop using deprecated Octal escape literals: Resolved
• Stop using depredated SynchronizedSet: Resolved