You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want to support additional query features such as arithmetic, a single logical query will likely map to several KairosDB queries in which case the ArithmeticQueryExecutor would want to
decompose their query and then
pass it into the downstream executor.
To avoid the overhead of creating the query and then serializing it to conform to the interface, clients should be able to pass structured queries directly to the executors. The signature currently does not allow for passing in a structured query and so we would need to expose that, perhaps using a generic:
interfaceQueryExecutor<T> { // T - RequestTypeCompletionStage<MetricsQueryResponse> executeRaw(finalStringserializedQuery);
CompletionStage<MetricsQueryResponse> execute(finalTrequest);
}
Executors can opt-out of this behavior by implementing QueryExecutor<Void>.
The text was updated successfully, but these errors were encountered:
Right now QueryExecutors are opaque, the signature of execute is essentially
If we want to support additional query features such as arithmetic, a single logical query will likely map to several KairosDB queries in which case the
ArithmeticQueryExecutor
would want toTo avoid the overhead of creating the query and then serializing it to conform to the interface, clients should be able to pass structured queries directly to the executors. The signature currently does not allow for passing in a structured query and so we would need to expose that, perhaps using a generic:
Executors can opt-out of this behavior by implementing
QueryExecutor<Void>
.The text was updated successfully, but these errors were encountered: