Håvard M. Ottestad

Also I think that we are currently building a new evaluation strategy and optimizer pipeline for each query.

It's currently the strategy that is responsible for optimizing the query. I still feel that it's a natural place to add the extension to support sail level optimizers.

> I am ok with this as is. @hmottestad would you mind testing out how this codes by updating the Fedx optimization steps with this approach. As there the strategy...

The way the optimizer pipeline can be set from the `StrictEvaluationStrategyFactory` when instantiating a `StrictEvaluationStrategy` is quite odd. It first instantiates the strategy, then checks if it should override the...

Yep, I want to try the pipeline-factory approach.

Marked this as stale to signal that the PR hasn't been active for a while and that we should consider closing it.

Currently exploring how to improve the performance of concurrent access to the MemoryStore. The largest things seem to be overhead in locking/synchronization (+tracking locks) and lack of concurrent access to...

Marked this as stale to signal that the PR hasn't been active for a while and that we should consider closing it.

In the ShaclSail I ended up writing my own rdf list implementation because of this issue. My fix was to not generate the type statements. https://github.com/eclipse/rdf4j/blob/main/core/sail/shacl/src/main/java/org/eclipse/rdf4j/sail/shacl/ast/ShaclAstLists.java

Would you be interested in making a PR with the fix and some tests?