Halyard
Halyard copied to clipboard
Halyard is an extremely horizontally scalable Triplestore with support for Named Graphs, designed for integration of extremely large Semantic Data Models, and for storage and SPARQL 1.1 querying of th...
Bumps derby from 10.12.1.1 to 10.14.2.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
Bumps derby from 10.12.1.1 to 10.14.2.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
I am considering trying Halyard + Rdf4j. I hope to find any document which states its high availability possibilities / capacities. Is there anybody can help? Thanks, -xiaoshan
Bumps [junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1. Release notes Sourced from junit's releases. JUnit 4.13.1 Please refer to the release notes for details. JUnit 4.13 Please refer to the release notes...
Halyard is powerful distributed triplestore, instantly answering majority of SPARQL queries, however weak in some complex operations (like ORDER BY and GROUP BY) and complicated to implement a custom code...
If I configure a repository with Push, the performance of the SPARQL query is extremely slow and might not return within timeout. If I create the same repository but with...
The easiest way to demonstrate this is to set HalyardTupleExprEvaluation.MAX_QUEUE_SIZE = 1 then try to evaluate "ASK {}". HalyardTupleExprEvaluation.evaluateTupleExpr(root.pipe, expr, bindings) needs to be called on a background thread.
This is a clone of the RDF4J issue that also needs to be fixed in Halyard: https://github.com/eclipse/rdf4j/issues/1405 Several tests in HalyardComplexSPARQLQueryTest have to be skipped due to the issue.
When you have a SPARQL query with nested `OPTIONAL` clauses, such as the following, it's performance is poor, typically causing timeouts. ```rq PREFIX bibo: PREFIX dcterms: SELECT * WHERE {...