Hi,
the pull request now also contains a commit changing URI to IRI.
Side question: I used to amend my branch and force push the updates (i.e. to avoid too many commits and have a clean history). Unfortunately this is now reflected in the conversation stream of
https://github.com/eclipse/rdf4j-storage/issues/71 (even though I did the changes in my own fork of the repository).
What is the best practice to avoid this? Should I avoid referencing #71 in my commit messages, and reference it only in the PR?
Besides that the change is now good from my side, except for the ElasticSearch Integration test. Unfortunately I cannot get it run from Maven (even with the workaround thing that works from Eclipse). Likely there are differences in the classpath or the way system properties are passed?
@Bart: If we do the upgrade we should also update jackson to 2.9.x, as far as I know there is a security vulnerability in one of the jackson libraries. We are already using 2.9.5 at the moment, so this upgrade should be straight forward. I might provide a change for this in the next week.