[
https://issues.apache.org/jira/browse/HIVE-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101485#comment-14101485
]
Na Yang commented on HIVE-7717:
-------------------------------
Hi Brock,
Those tests passed locally. I re-generated some of the test results and found
out that the explain plans are the same between test runs, but the result data
have different order although the same number of rows are returned. Let me
re-ran those tests and upload a new patch.
Thanks,
Na
> 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
> Affects Versions: spark-branch
> Reporter: Na Yang
> Assignee: Na Yang
> Attachments: HIVE-7717.1-spark.patch, HIVE-7717.2-spark.patch
>
>
> 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)
