You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/03/20 13:15:39 UTC

[jira] [Created] (SPARK-6433) hive tests to import spark-sql test JAR for QueryTest access

Steve Loughran created SPARK-6433:
-------------------------------------

             Summary: hive tests to import spark-sql test JAR for QueryTest access
                 Key: SPARK-6433
                 URL: https://issues.apache.org/jira/browse/SPARK-6433
             Project: Spark
          Issue Type: Improvement
          Components: Build, SQL
    Affects Versions: 1.4.0
            Reporter: Steve Loughran
            Priority: Minor


The hive module has its own clone of {{org.apache.spark.sql.QueryPlan}} and {{org.apache.spark.sql.catalyst.plans.PlanTest}} which are copied from the spark-sql module because it's "hard to have maven allow one subproject depend on another subprojects test code"

It's actually relatively straightforward
# tell maven to build & publish the test JARs
# import them in your other sub projects

There is one consequence: the JARs will also end being published to mvn central. This is not really a bad thing; it does help downstream projects pick up the JARs too. It does become an issue if a test run depends on a custom file under {{src/test/resources}} containing things like EC2 authentication keys, or even just log4.properties files which can interfere with each other. These need to be excluded -the simplest way is to exclude all of the resources from test 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