We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Disclaimer: the query is convoluted, I'm not sure if there's any realistic use case.
CQL:
create table foo(k int primary key, v int); insert into foo(k,v) values(1,1);
GraphQL:
mutation @atomic { bulkInsertfoo(values: [{ k: 1, v: 2 }, { k: 1, v: 3 }], ifNotExists: true) { applied value { k } } insertfoo(value: { k: 1, v: 4 }, ifNotExists: true) { applied value { v } } }
This causes:
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 at io.stargate.graphql.schema.cqlfirst.dml.fetchers.DmlFetcher.toListOfMutationResults(DmlFetcher.java:122)
The methods assumes that if there are rows then it's one per input value, but if the batch is conditional, only one row is returned.
The text was updated successfully, but these errors were encountered:
Possibly a more likely use case once we fix #1069.
Sorry, something went wrong.
GraphQL CQL-first: Fix handling of conditional batches
9d437a8
Fixes #1067 Fixes #1068
2f2f1b1
GraphQL CQL-first: Fix handling of conditional batches (#1078)
8967664
Successfully merging a pull request may close this issue.
Disclaimer: the query is convoluted, I'm not sure if there's any realistic use case.
CQL:
GraphQL:
This causes:
The methods assumes that if there are rows then it's one per input value, but if the batch is conditional, only one row is returned.
The text was updated successfully, but these errors were encountered: