hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-7717) Add .q tests coverage for "union all" [Spark Branch]
Date Fri, 15 Aug 2014 03:29:19 GMT

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

Brock Noland updated HIVE-7717:
-------------------------------

    Issue Type: Sub-task  (was: Test)
        Parent: HIVE-7292

> Add .q tests coverage for "union all" [Spark Branch]
> ----------------------------------------------------
>
>                 Key: HIVE-7717
>                 URL: https://issues.apache.org/jira/browse/HIVE-7717
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Na Yang
>            Assignee: Na Yang
>
> Add automation test coverage for "union all", by searching through the q-tests in "ql/src/test/queries/clientpositive/"
for union tests (like union*.q) and verifying/enabling them on spark.
> Steps to do:
> 1.  Enable a qtest <q-test-name>.q in itests/src/test/resources/testconfiguration.properties
by adding the .q test files to spark.query.files.
> 2.  Run mvn test -Dtest=TestSparkCliDriver -Dqfile=<q-test-name>.q -Dtest.output.overwrite=true
-Phadoop-2 to generate the output (located in ql/src/test/results/clientpositive/spark). 
File will be called <q-test-name>.q.out.
> 3.  Check the generated output is good by verifying the results.  For comparison, check
the MR version in ql/src/test/results/clientpositive/<q-test-name>.q.out.  The reason
its separate is because the explain plan outputs are different for Spark/MR.
> 4.  Checkin the modification to testconfiguration.properties, and the generated q.out
file as well.  You only have to generate the output once.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message