Hi,
an alternative to using the client that Pouria suggested would be to add
"mode=asynchronous-deferred" as an HTTP parameter when talking to the
API. In
that case the query should be evaluated completely and an HTTP response
should
come back - however without the result. Instead the response
You may find the following client useful.
It works against the HTTP, runs query workload for one or more iterations
and dumps the response time per query/iteration in a stats file.
https://github.com/pouriapirz/asterixClient
Pouria
On Fri, Dec 2, 2016 at 10:45 AM, Thor Martin Abrahamsen
Additional note: @Till: Yes. It happened again for the same hash-join
query. As we can see in the bold part of the following CC.log, one node
alone was executing for two hours.
Dec 01, 2016 10:41:56 PM
org.apache.hyracks.control.cc.scheduler.ActivityClusterPlanner
planActivityCluster
INFO: Plan
