Hi Havard,
we have been able to validate the RDF4J 5.0 M1 build in our product and also to do some smoke testing.
Here is our feedback:
Code-Level
- Main change in our code-base was the removal of the Exception generic parameter from CloseableIteration
- For some algebra nodes we had to implement QueryModelNode#replaceChildNode and QueryModelNode#visitChildrent
- Some smaller changes, e.g. replacing Iterations.close(iter) with iter.close
Execution time:
- No compatibility issues discovered in quick smoke testing of our application
I noticed that the @Deprecated annotations are still present on the central interfaces (e.g. CloseableIteration). For myself - where I am using the Eclipse IDE - this means that I still have tons of deprecation warnings. Ideally for the next milestone build and the final 5.0 RDF4J release the deprecated annotations can be removed entirely.
Another side question for RDF4J 5.0: to my knowledge RDF4J still uses HTTP client 4.5.x. In our application we have seen recently one limitation of the old http client version, namely that it does hot HTTP/2 (for which support is only added in the http client 5.x). We could solve this on the proxy level, but as we are doing a major release of RDF4J would it make sense to look into the http client as well? I suspect that the migration would not be too difficult, but haven't checked. Is this maybe already tracked and on the radar?
Thanks again Havard for driving the RDF4J project.
Best,
Andreas