-
Notifications
You must be signed in to change notification settings - Fork 0
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
Pipelining e-Entity + e-Link, the second service fails #69
Comments
@ArneBinder please try to reproduce this bug and find out whats wrong. |
The problem seems to rely on com.hp.hpl.jena.query. When executing the following e-link request:
with a small modification in exception/error passing I get:
Calling the referenced dbpedia sparql endpoint with the query mentioned in the exception gives this result:
Trying to read the char |
@m1ci the bug originates from e-link. Please take a look at the bug. |
The issue is within Jena v 2.11.2 with the – char which is considered as invalid. We should consider upgrading Jena. |
I think that Jena dependency is only defined in FREMECommon. I will update it to the latest version. |
please upgrade to Jena 2.13.0 |
@ArneBinder please update FREMECommon Jena dependency to Jena 2.13.0 and check if the bug is fixed by that. |
We tried the upgrade to Jena 2.13.0 and it did not solve the problem. We cannot upgrade to higher versions of Jena because the LDF client is not compatible to higher Jena versions. So we cannot fix this bug. |
See 6.4 Escape Sequences Seems that in turtle, the IRI cannot contain I asked that DBpedia endpoint - it returns more than 13 000 resource IRIs containg character So one solution would be asking the endpoint for other rdf syntax, e.g triples. [in case if e-link asks n3/turtle from endpoints]. |
great idea! thanks @andish for the research and the proposal. |
Any development on this issue? |
No new developments. I put this issue on the agenda of next developers call. |
On todays dev call we agreed that @sandroacoelho and @m1ci will work on the issue |
the issue is fixed, @andish @borriellom please check! |
It's fixed. Thank you! |
Fixed on freme-live through the release |
Request:
Response
This error is input-text-specific, some other cases there is no error.
The text was updated successfully, but these errors were encountered: