Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Primes using queryPattern are not returned from /prime-simple-query #135

Open
jbridger opened this issue Feb 8, 2016 · 2 comments
Open

Comments

@jbridger
Copy link
Contributor

jbridger commented Feb 8, 2016

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.PrimingRequestBuilder prime = PrimingRequest.queryBuilder()
                .withQueryPattern("INSERT INTO ...")
                .withThen(then().withResult(PrimingRequest.Result.valueOf(exception)));
@chbatey
Copy link
Member

chbatey commented Feb 16, 2016

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?

@jbridger
Copy link
Contributor Author

jbridger commented Mar 8, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants