Releases: eclipse-rdf4j/rdf4j
RDF4J 4.3.6
RDF4J 4.3.6 is now available. This is a patch release fixing 4 bugs.
For more details, have a look at the release notes.
Links
Download RDF4J
release notes.
RDF4J 4.3.5
RDF4J 4.3.5 is a patch release that fixes 5 issues.
For a complete overview, see all issues fixed in 4.3.5.
Acknowledgements
This release was made possible by contributions from Manuel Fiorelli and Håvard M. Ottestad.
RDF4J 4.3.4
RDF4J 4.3.4 is a patch release that fixes 2 issues.
For a complete overview, see all issues fixed in 4.3.4.
Acknowledgements
This release was made possible by contributions from Håvard M. Ottestad, Matthew Nguyen, pulquero, Jerven Bolleman and Jeen Broekstra.
RDF4J 4.3.2
RDF4J 4.3.2 is a patch release that fixes 4 issues.
For a complete overview, see all issues fixed in 4.3.2.
Acknowledgements
This release was made possible by contributions from Andreas Schwarte, Johan Van Noten, Håvard M. Ottestad and Borislav Bonev.
RDF4J 4.3.1
RDF4J 4.3 is a minor release that fixes 34 issues.
A few notable features
- Solr, Lucene and Elasticsearch
- Solr and Lucene are upgraded to 8.9.0 and Elasticsearch is upgraded to 7.15.2
- Support for complex Lucene queries
- Support for customizing the query analyzer in Lucene and Elasticsearch
- SHACL
- A standalone SHACL Validator
- User defined SPARQL queries in SHACL Constraints and Targets
- Support for sequence paths and alternate paths
- Migration of more tests to Junit 5
- Remove Java EE dependency from core libraries
- Improvements to the extended query evaluation 1, 2
- Several performance improvements 1, 2, 3, 4
For a complete overview, see all issues fixed in 4.3.
There are no more planned minor releases for 4.x.x. The next planned release is 5.0.0.
Due to a backwards compatibility bug we recommend using 4.3.1
.
Acknowledgements
This release was made possible by contributions from Andreas Schwarte, Håvard M. Ottestad, Erik Godding Boye, Jeen Broekstra, Jerven Bolleman, Bart Hanssens, Wolfgang Schell, Mike Glazer, Patrick Wyler and Antoine Willerval.
4.2.4
RDF4J 4.2.4 is a patch release that fixes 6 issues.
For a complete overview, see all issues fixed in 4.2.4.
RDF4J 4.2.3
RDF4J 4.2.3 is a patch release that fixes 9 issues.
For those who are using RDF4J tests in their own code you should note that we are currently working on migrating from JUnit 4 to JUnit 5.
For a complete overview, see all issues fixed in 4.2.3.
Acknowledgements
This release was made possible by contributions from Erik Godding Boye, Dominik Kunz, Håvard M. Ottestad, Martina Dimova, Jeen Broekstra, Tom Dalton, Jerven Bolleman and Dzeri96.
RDF4J 4.2.2
RDF4J 4.2.2 is now available. This is a patch release fixing 3 bugs.
For more details, have a look at the release notes.
RDF4J 4.2.1
RDF4J 4.2.1 is now available. This is a patch release fixing 11 bugs, 3 of which are security fixes.
For more details, have a look at the release notes.
RDF4J 4.2.0
RDF4J 4.2.0 is a minor release introducing support for custom SPARQL aggregate functions as well as several performance improvements and bug fixes.
Aggregate functions
The support for custom SPARQL aggregate functions has allowed us to implement functions for standard deviation and variance using Apache Commons Math3.
IRI | Description |
---|---|
http://rdf4j.org/aggregate#stdev | Standard deviation using sampling. |
http://rdf4j.org/aggregate#stdev_population | Standard deviation using statistical population. |
http://rdf4j.org/aggregate#variance | Variance using sampling. |
http://rdf4j.org/aggregate#variance_population | Variance using statistical population. |
Query example
SELECT (<http://rdf4j.org/aggregate#stdev>(?o) AS ?stdev) WHERE {
?s ?p ?o .
}
Performance
More accurate query statistics for the LMDB Store drastically improves query performance. The LMDB Store can already scale to considerably larger datasets than the NativeStore and now also matches the performance for smaller datasets.
Validation performance for small transactions on large databases has been improved by batching together more operations when analyzing the changes in a transaction.
For a complete overview, see all issues fixed in 4.2.0.