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
Primed queries using query patterns do not get returned in the /prime-simple-query endpoint. The prime query does work, as we get the expected primed behaviour. Same result from priming through the Java priming client or directly through the JSON API.
Also checked the /prime-prepared-query just in case, and it didn't appear there which would be expected.
Example prime with query pattern using Java:
PrimingRequest.PrimingRequestBuilderprime = PrimingRequest.queryBuilder()
.withQueryPattern("INSERT INTO ...")
.withThen(then().withResult(PrimingRequest.Result.valueOf(exception)));
The text was updated successfully, but these errors were encountered:
Thanks for reporting. I am not planning on doing any work on returning the primes going forward as I don't have any use cases for it. Why do you need it?
Our use cases for retrieving primes is to confirm we've primed successfully, to see what has been primed, and sometimes to use data from the priming client and activity client in our automated tests.
With that said, we no longer need them as we've switched from using query patterns to the recently introduced multi primes.
Primed queries using query patterns do not get returned in the /prime-simple-query endpoint. The prime query does work, as we get the expected primed behaviour. Same result from priming through the Java priming client or directly through the JSON API.
Also checked the /prime-prepared-query just in case, and it didn't appear there which would be expected.
Example prime with query pattern using Java:
The text was updated successfully, but these errors were encountered: