You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/07/31 20:32:05 UTC
[jira] [Commented] (JENA-1004) Dynamic datasets inconsistently
supported in Fuseki.
[ https://issues.apache.org/jira/browse/JENA-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649613#comment-14649613 ]
Andy Seaborne commented on JENA-1004:
-------------------------------------
Possible solutions for queries:
1. _Put all dynamic dataset support in Fuseki_
Downside - may result in non-transactional execution in TDB (needs investigating).
2. _Test the type of dataset and adapt_
Downside - Building in the known storage solutions is a short-term approach.
> Dynamic datasets inconsistently supported in Fuseki.
> ----------------------------------------------------
>
> Key: JENA-1004
> URL: https://issues.apache.org/jira/browse/JENA-1004
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.0.0
> Reporter: Andy Seaborne
>
> Dynamic datasets, where the dataset to query is constructed out of the graphs of the underlying dataset behave differently for in-memory and TDB datasets.
> [TDB supports them natively|https://jena.apache.org/documentation/tdb/dynamic_datasets.html] when {{FROM}}, {{FROM NAMED}} are used.
> {{SPARQL_QueryDataset#decideDataset}} provides the feature for SPARQL protocol ({{default-graph-uri=}}, {{named-graph-uri=}} externally to the dataset.
> Other datasets do not support the feature. Henc, in-memory dataset services does not support it when {{FROM}}, {{FROM NAMED}} used but does when {{default-graph-uri=}}, {{named-graph-uri=}} used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)