Skip to content
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

Merge main into develop #63

Open
wants to merge 41 commits into
base: develop
Choose a base branch
from
Open

Merge main into develop #63

wants to merge 41 commits into from

Conversation

github-actions[bot]
Copy link

Automatically generated PR to keep develop in sync with main.

USE MERGE COMMIT TO MERGE THIS PR.

See merge_main_to_develop.yml.

fkleedorfer and others added 30 commits June 2, 2024 15:28
Added a link to the Jelly serialization format implementation for RDF4J: https://w3id.org/jelly/jelly-jvm

Jelly is a binary RDF format with a strong performance focus. The implementation for RDF4J can be either used as a Maven dependency, or as a JAR plugin that you drop into your classpath.

Jelly was also implemented for Apache Jena. An implementation for rdflib is planned.
Signed-off-by: Håvard Ottestad <[email protected]>
Signed-off-by: Håvard Ottestad <[email protected]>
…tion in FedX

This change adds preparational infrastructure for having different
implementations of schedulers. Configuration is here prepared by means
of defining a "SchedulerFactory" interface with a default implementation
aside (which essentially mimics the current behavior).

Note that for ease of development some aspects of
ControlledWorkerScheduler are made accessible to sub-classes. The idea
is that in the end version there is an abstract scheduler class
providing shared functionality and different implementation (e.g. the
current FIFO one and a fair implementation)
…anges

- for minor version compatibility the type of the "_taskQueue" field in
the scheduler cannot be changed (to non-final). Hence, for now we use a
dedicated protected initialization method. In the future (next major
release) the idea is to leave the queue entirely managed by the executor
service.
- refinements and clarifications to the javadoc
Previously we introduced support for left bind joins in FedX. The case
of empty left bind joins (i.e. where the clause inside the OPTIONAL does
not provide any statements) was not handled and resulted in an exception

This change now adds support for empty optional joins and passes the
results from the left-handside through.
…KEY and MAX_DOCUMENTS_KEY to DEFAULT_NUM_DOCS_KEY
…t the distinct values when applied to the union of multiple graphs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants