[
https://issues.apache.org/jira/browse/SPARK-23629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535944#comment-16535944
]
Bruce Robbins commented on SPARK-23629:
---------------------------------------
Whatever was causing this, it is now gone away. Problem is no longer
reproducible on the master.
> Building streaming-kafka-0-8-assembly or streaming-flume-assembly adds
> incompatible jline jar to assembly
> ---------------------------------------------------------------------------------------------------------
>
> Key: SPARK-23629
> URL: https://issues.apache.org/jira/browse/SPARK-23629
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.3.0
> Reporter: Bruce Robbins
> Priority: Minor
>
> When you build spark-streaming-flume-assembly or streaming-kafka-0-8-assembly
> (so that you can run the python tests), you get two versions of the jline jar
> in assembly:
> {noformat}
> bash-3.2$ find assembly -name "*jline*.jar"
> assembly/target/scala-2.11/jars/jline-0.9.94.jar
> assembly/target/scala-2.11/jars/jline-2.12.jar
> bash-3.2$
> {noformat}
> This causes the org.apache.spark.sql.hive.thriftserver.CliSuite tests to fail:
> {noformat}
> [info] 2018-03-08 07:35:55.854 - stderr> [ERROR] Terminal initialization
> failed; falling back to unsupported
> [info] 2018-03-08 07:35:55.855 - stderr>
> java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but
> interface was expected
> {noformat}
> It also causes spark-shell to throw an exception on start-up, but otherwise
> seems to work OK.
>
--
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
