[
https://issues.apache.org/jira/browse/JENA-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022138#comment-17022138
]
Andy Seaborne commented on JENA-1825:
-------------------------------------
Each optimization has a context settings to control whether it is on or off.
This can be global, per dataset or per query.
If this ticket is about exposing that to a Fuseki request, and modifying the
extended query syntax, I'm not so keen exposing internal details in this way.
Detail change over time but query pragma make them public contract.
> disabling some optimizations
> ----------------------------
>
> Key: JENA-1825
> URL: https://issues.apache.org/jira/browse/JENA-1825
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 3.14.0
> Reporter: Elie Roux
> Priority: Minor
>
> It would be useful to have a mechanism to disable some optimizations in
> SPARQL. The reason is that sometimes optimizations hinder performances. For
> instance FILTERs with long INs result in large unions which are less
> performant than a filter on a small dataset. This really depends on the
> queries but can have a big impact.
> See also https://github.com/w3c/sparql-12/issues/105
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
