dongjoon-hyun opened a new pull request #23502: [SPARK-22128][CORE] Add 
`paranamer` dependency to `core` module
URL: https://github.com/apache/spark/pull/23502
 
 
   ## What changes were proposed in this pull request?
   
   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
   
   The following is the dependency tree from the Spark application.
   
   **BEFORE**
   ```
   $ 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
   ```
   
   **AFTER**
   ```
   [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]       \- com.thoughtworks.paranamer:paranamer:jar:2.8:compile
   ```
   
   ## How was this patch tested?
   
   Pass the Jenkins. And manually test with the sample app is running.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to