[ https://issues.apache.org/jira/browse/SPARK-26583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738746#comment-16738746 ]
Dongjoon Hyun commented on SPARK-26583: --------------------------------------- This is a minor issue, but this should be fixed before Spark 3.0.0 because this affects Spark applications . For Spark 2.4.0 Scala 2.12 artifacts, the situation is the same. Of course, users can add `paranamer` dependency into their pom. > Add `paranamer` to `core` module > -------------------------------- > > Key: SPARK-26583 > URL: https://issues.apache.org/jira/browse/SPARK-26583 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 2.4.0, 3.0.0 > Reporter: Dongjoon Hyun > Priority: Blocker > > With Scala-2.12 profile, Spark application fails while Spark is okay. For > example, our documented `SimpleApp` example fails because it doesn't use > `paranamer 2.8` and hits SPARK-22128. > https://dist.apache.org/repos/dist/dev/spark/3.0.0-SNAPSHOT-2019_01_09_13_59-e853afb-docs/_site/quick-start.html > {code} > $ mvn dependency:tree -Dincludes=com.thoughtworks.paranamer > [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ simple --- > [INFO] my.test:simple:jar:1.0-SNAPSHOT > [INFO] \- org.apache.spark:spark-sql_2.12:jar:3.0.0-SNAPSHOT:compile > [INFO] \- org.apache.spark:spark-core_2.12:jar:3.0.0-SNAPSHOT:compile > [INFO] \- org.apache.avro:avro:jar:1.8.2:compile > [INFO] \- com.thoughtworks.paranamer:paranamer:jar:2.7:compile > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org