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_sqlpp/prim-idx-search.sqlpp b/asterix-app/src/test/resources/optimizerts/queries_sqlpp/prim-idx-search.sqlpp
index 1bf0d81..a928a25 100644
--- a/asterix-app/src/test/resources/optimizerts/queries_sqlpp/prim-idx-search.sqlpp
+++ b/asterix-app/src/test/resources/optimizerts/queries_sqlpp/prim-idx-search.sqlpp
@@ -37,12 +37,12 @@
}
create nodegroup group1 if not exists on
- nc1,
- nc2
+ asterix_nc1,
+ asterix_nc2
;
create table Orders(OrderType) primary key o_orderkey on group1;
-write output to nc1:"/tmp/prim_index_search.adm"
+write output to asterix_nc1:"/tmp/prim_index_search.adm"
select element {'o_orderkey':o.o_orderkey,'o_custkey':o.o_custkey}
from Orders as o
where (o.o_orderkey = 34)