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

SPARQL-over-HTTP errors should be surfaced in the log/response #1685

Open
ash-mcc opened this issue Jan 7, 2022 · 0 comments
Open

SPARQL-over-HTTP errors should be surfaced in the log/response #1685

ash-mcc opened this issue Jan 7, 2022 · 0 comments
Labels
1.x enhancement New feature or request

Comments

@ash-mcc
Copy link

ash-mcc commented Jan 7, 2022

Background

I added xtdb-rdf 1.19.0 lib to xtdb-in-a-box 0.0.2 (xtdb-core 1.19.0)’s deps.edn. Then, against it, curl http://localhost:9999/_xtdb/status was successful. But curl http://localhost:9999/_xtdb/sparql?query=SELECT ?o WHERE { ?s ?p ?o . } failed with an UnsupportedOperationException. (I did URLEncode that query arg when I actually try it.) Jetty’s DEBUG log entries showed the corresponding incoming HTTP request but they didn’t help me to figure out what the problem might be. More logging?...

The cause of the Exception

xtdb.sparql/sparql->datalog throws (line 223) an UnsupportedOperationException with the message Does not support variables in predicate position: ?p. But that message isn't surfaced in the logs or the HTTP response.

TODO

Jeremy suggested that I created this issue to have that message surfaced in the logs.

@refset refset added this to Backlog in XTDB Development via automation Jan 7, 2022
@refset refset added the enhancement New feature or request label Jan 7, 2022
@refset refset changed the title Surface the "Does not support variables in predicate position" error message in the log SPARQL-over-HTTP errors should be surfaced in the log/response Jan 7, 2022
@jarohen jarohen added the 1.x label Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

3 participants