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/09/14 17:59:20 UTC
[jira] [Updated] (SPARK-17542) Compiler warning in
UnsafeInMemorySorter class
[ https://issues.apache.org/jira/browse/SPARK-17542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-17542:
------------------------------
Issue Type: Improvement (was: Bug)
There are unfortunately a number of warnings, and I don't think we want a JIRA for each of them. Somebody whacks a lot of them periodically. So, sure, they're good to resolve but I'd be more interested in sweeps that clean up as many warnings as possible. Some are un-suppressable and un-resolvable, like tests for deprecated methods in Scala. This isn't a bug though.
> Compiler warning in UnsafeInMemorySorter class
> ----------------------------------------------
>
> Key: SPARK-17542
> URL: https://issues.apache.org/jira/browse/SPARK-17542
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Frederick Reiss
> Priority: Trivial
> Labels: starter
>
> *This is a small starter task to help new contributors practice the pull request and code review process.*
> When building Spark with Java 8, there is a compiler warning in the class UnsafeInMemorySorter:
> {noformat}
> [WARNING] .../core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeInMemorySorter.java:284: warning: [static]
> static method should be qualified by type name, TaskMemoryManager, instead of
> by an expression
> {noformat}
> Spark should compile without these kinds of warnings.
--
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