Closed coret closed 5 months ago
If this is indeed a workaround for GraphDB, I think the best solution is to change the check for valid URL's and add a unit test for this case. The solution would then be to strip sparql@
from the endpoint before testing the validity of the URL.
:tada: This issue has been resolved in version 1.0.2 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
I'm using endpoint: sparql@https://www.goudatijdmachine.nl/sparql/repositories/nafotocollectie
in my config (on the nafoto pipeline) but I immediately get an error:
The Iterator did not run succesfully, it could not get the results from the endpoint
https://www.goudatijdmachine.nl/sparql/repositories/nafotocollectie (offset: 0, limit 10): Could not retrieve
https://www.goudatijdmachine.nl/sparql/repositories/nafotocollectie (HTTP status 400)
The GraphDB logfile show the following error:
[INFO ] 2024-05-29 20:45:23,181 [repositories/nafotocollectie | c.o.f.s.GraphDBProtocolExceptionResolver]
Client sent bad request (400)
org.eclipse.rdf4j.http.server.ClientHTTPException: Missing parameter: query
@coret Fixed. Please remove the sparql@
prefix from your config as that is now automatically done.
:tada: This issue has been resolved in version 1.4.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
I get a HTTP status 400 error (Missing parameter: query) when I use an GraphDB endpoint. No problem when I use the Jena endpoint https://service.archief.nl/sparql
When I use the tip from @rubensworks in https://github.com/comunica/comunica/issues/962 (prepend sparql@ to the endpoint URL) the query does return results:
However, I cannot specify
endpoint: sparql@https://www.goudatijdmachine.nl/sparql/repositories/nafotocollectie
in my ld-workbench config.yaml:Should the ld-workbench use Comunica in another way?