spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Rosen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-4914) Two sets of datanucleus versions left in lib_managed after running dev/run-tests
Date Tue, 23 Dec 2014 20:55:14 GMT

     [ https://issues.apache.org/jira/browse/SPARK-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Rosen resolved SPARK-4914.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.1
                   1.3.0

Issue resolved by pull request 3756
[https://github.com/apache/spark/pull/3756]

> Two sets of datanucleus versions left in lib_managed after running dev/run-tests
> --------------------------------------------------------------------------------
>
>                 Key: SPARK-4914
>                 URL: https://issues.apache.org/jira/browse/SPARK-4914
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.2.0
>            Reporter: Cheng Lian
>            Priority: Minor
>             Fix For: 1.3.0, 1.2.1
>
>
> The {{dev/run-tests}} script first does a clean compile with Hive 0.12.0, and then builds
assembly jar for unit testing with Hive 0.13.1 *without* cleaning. This left two sets of datanucleus
jars under the {{lib_managed}} folder, one set depended by Hive 0.12.0, another by Hive 0.13.1.
> This behavior sometimes messes up class paths and makes {{CliSuite}} and {{HiveThriftServer2Suite}}
fail, because these two suites spawn external processes that depends on those datanucleus
jars.



--
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


Mime
View raw message