Fix for issue 813 - enabling prefix btree search with non-matching predicates
Change-Id: I59eb43afa7dbcabd7f43269566d75c9361c55386
Reviewed-on: http://fulliautomatix.ics.uci.edu:8443/171
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <bamousaa@gmail.com>
diff --git a/asterix-app/src/test/resources/optimizerts/queries/btree-index/btree-secondary-37.aql b/asterix-app/src/test/resources/optimizerts/queries/btree-index/btree-secondary-37.aql
index 7c155ce..a771083 100644
--- a/asterix-app/src/test/resources/optimizerts/queries/btree-index/btree-secondary-37.aql
+++ b/asterix-app/src/test/resources/optimizerts/queries/btree-index/btree-secondary-37.aql
@@ -1,12 +1,12 @@
/*
* Description : BTree Index verification test
- * : This test is intended to verify that the secondary BTree index is NOT used in the optimized query plan.
+ * : This test is intended to verify that the secondary BTree index is NOT used
+ * : in the optimized query plan.
* Expected Result : Success
* Date : 13th Aug 2012
*/
-// THE BTREE INDEX IN THIS CASE SHOULD NOT BE PICKED UP!!!!
-// Verify that the optimized query plan does not have the BTree search
+// Negative test - BTree index should NOT be used in query plan
drop dataverse test if exists;
create dataverse test;
@@ -25,5 +25,5 @@
create index sec_Idx on testdst(fname,lname);
for $emp in dataset('testdst')
-where $emp.lname = "Kim"
+where $emp.fname != "Max"
return $emp