Run ExecutionTest w/integration test framework
I changed the default local.xml to use 2 NCs with
2 partitions each like AsterixHyracksIntegrationUtil
so that the results will match despite using simple
string compare to determine correctness.
There is also one test in particular (big-object-join)
that I had to add an artificial order by clause to
to deal with different results.
Issues outstanding:
- HDFS in ClusterExecutionIT needs to be thought out
Change-Id: I423f2a7c77839b999d466dd5cace302574d956c0
Reviewed-on: https://asterix-gerrit.ics.uci.edu/525
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Chris Hillery <ceej@lambda.nu>
diff --git a/asterix-app/src/test/resources/optimizerts/queries/unnest-to-join_01.aql b/asterix-app/src/test/resources/optimizerts/queries/unnest-to-join_01.aql
index defbcbf..52e56d3 100644
--- a/asterix-app/src/test/resources/optimizerts/queries/unnest-to-join_01.aql
+++ b/asterix-app/src/test/resources/optimizerts/queries/unnest-to-join_01.aql
@@ -25,7 +25,7 @@
create dataverse test;
use dataverse test;
-write output to nc1:"rttest/unnest-to-join_01.adm";
+write output to asterix_nc1:"rttest/unnest-to-join_01.adm";
for $x in [1,2,3,4,5,6]
for $y in [4,5,6,7,8,9]