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 2017/11/30 08:22:01 UTC
[jira] [Updated] (SPARK-22660) Use position() and limit() to fix
ambiguity issue in scala-2.12 and JDK9
[ https://issues.apache.org/jira/browse/SPARK-22660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-22660:
------------------------------
Priority: Minor (was: Major)
You don't need reflective calls here; typically you just need a cast. That kind of thing can be safely added without breaking Scala 2.11 or Java 8.
[~kellyzly] let's not keep opening JIRAs for all these types of cases. We do not support Java 9 or Scala 2.12 yet, for reasons larger than this. It's OK to future-proof or clarify the code if it doesn't break things.
But one of your proposed changes already seems to do that.
> Use position() and limit() to fix ambiguity issue in scala-2.12 and JDK9
> ------------------------------------------------------------------------
>
> Key: SPARK-22660
> URL: https://issues.apache.org/jira/browse/SPARK-22660
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 2.2.0
> Reporter: liyunzhang
> Priority: Minor
>
> Based on SPARK-22659
> 1. compile with -Pscala-2.12 and get the error
> {code}
> Use position() and limit() to fix ambiguity issue
> {code}
> spark_source/core/src/main/scala/org/apache/spark/executor/Executor.scala:455: ambiguous reference to overloaded definition, method limit in class ByteBuffer of type (x$1: Int)java.nio.ByteBuffer
> method limit in class Buffer of type ()Int
> match expected type ?
> val resultSize = serializedDirectResult.limit
> error
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org