[NO ISSUE][OTH] Use Request Stats When Printing Results on NC
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- When printing a result on an NC, use the stats object
of the original request rather than the object received
from the CC as part of the execute statement response
message. This is done because the metrics returned to the
user are generated from the stats object of the request.
- Add metrics test case to sqlpp test suite to test returning
metrics from NCQueryServiceServlet.
Change-Id: I54c3b3e72cfb0c2499a95bfc0f514dd5d6774293
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3444
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Ali Alsuliman <ali.al.solaiman@gmail.com>
diff --git a/asterixdb/asterix-app/src/test/resources/runtimets/testsuite_sqlpp.xml b/asterixdb/asterix-app/src/test/resources/runtimets/testsuite_sqlpp.xml
index 15c0702..7191d03 100644
--- a/asterixdb/asterix-app/src/test/resources/runtimets/testsuite_sqlpp.xml
+++ b/asterixdb/asterix-app/src/test/resources/runtimets/testsuite_sqlpp.xml
@@ -12342,4 +12342,11 @@
</compilation-unit>
</test-case>
</test-group>
+ <test-group name="metrics">
+ <test-case FilePath="metrics">
+ <compilation-unit name="full-scan">
+ <output-dir compare="Text">full-scan</output-dir>
+ </compilation-unit>
+ </test-case>
+ </test-group>
</test-suite>