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
Describe the bug
I have a query which works just fine with a couple of IRIs in it's VALUES ?targetClass { <iri1> <iri2> <iri3> ... } . Now if my code generates a larger query with hundreds of IRIs in ?targetClass, the client will give me a 400 (bad request) response.
Copying the same query, even with a lot of ?targetClasses, to the GraphDB Web UI and executing it will work.
To Reproduce
const query = 'add a big SPARQL query here'
GraphDbClient.validateSparqlQuery(query); // this passes just fine
const queryPayload = GraphDbClient.createSelectQueryPayload(query, limit);
let stream;
try {
stream = await this.client.query(queryPayload);
} catch (error) {
// error 400 is caught here
}
Expected behavior
Independent of the query length, it should be sent without a 400 error.
Library version [e.g. 1.1.2]
3.0.4
Node.js version [e.g. 8.16.0]
22.11.0
Describe the bug
I have a query which works just fine with a couple of IRIs in it's
VALUES ?targetClass { <iri1> <iri2> <iri3> ... } .
Now if my code generates a larger query with hundreds of IRIs in?targetClass
, the client will give me a400
(bad request) response.Copying the same query, even with a lot of
?targetClass
es, to the GraphDB Web UI and executing it will work.To Reproduce
Expected behavior
Independent of the query length, it should be sent without a 400 error.
Additional context
Rolling back to
3.0.3
solved the issue for now, so I believe that this change of 3.0.4 which is mentioned in CHANGELOG.md may be responsible for this:The text was updated successfully, but these errors were encountered: