-
Notifications
You must be signed in to change notification settings - Fork 30
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
working with jena/fuseki #62
Comments
thanks for reporting this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
After installation and configuration, being capable to add a dataset
Actual Behavior
Adding a dataset by naming it and giving an access point always gives the message
"There was no resource in the selected dataset! This might be due to the connection problems or because the estimated query execution time exceeds the configured limit. Please check the connection parameters of your dataset's Sparql endpoint or add resources to your dataset..."
in the interface
and the message
Error in sample facet config creation update query:
PREFIX ldr: https://github.com/ali1k/ld-reactor/blob/master/vocabulary/index.ttl#
PREFIX rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
PREFIX rdfs: http://www.w3.org/2000/01/rdf-schema#
PREFIX owl: http://www.w3.org/2002/07/owl#
Please also check if the configuration SPARQL endpoint is running and is updateable
...
in the console
Steps to Reproduce the Problem
Install ld-reactor, run it by typing
npm run build:windows
Specifications
Hypothesis
My configuration gives
host: 'localhost', port: 3030, path: '/ldreactor/sparql', endpointType: 'fuseki'
in server.js
By lsreactor seems to try to update this default dataset and with fuseki, the update point is /ldreactor/update while the query point is either /ldreactor/query or /ldreactor/sparql
So, it seems impossible to specify a different endpoint for query and for update.
The text was updated successfully, but these errors were encountered: