[
https://issues.apache.org/jira/browse/JENA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778665#comment-13778665
]
Priyaranjan commented on JENA-366:
----------------------------------
Andy,
DB2RDF stores the graph information in the database tables. The behavior of
uniondefaultgraph is significant when the query
does not specify any named graphs.
If uniondefaultgraph is true, we query all the graphs excluding those where the
graph is DEFAULT.
If uniondefaultgraph is false, we query only those graphs where the graph id is
DEFAULT.
The uniondefaultgraph setting is allowed by DB2RDF to be set in the store
context or the query context. When set in the store context, all queries that
are executed on the store will obey the uniondefaultgraph settings. However if
it is set only in query context, then it is valid only for that execution of
the query.
If this behavior can not be generalized, then we can close this task item. We
have the following workaround.
When using with FUSEKI, since we dont have a mechanism to set UnionDefaultGraph
while running the queries, we advise the end users to create two
DatasetAssemblers one with UnionDefaultgraph set to true and the other to
false. And query the datasets appropriately.
> Support for setting UnionDefaultGraph while running SPARQL queries on FUSEKI
> ----------------------------------------------------------------------------
>
> Key: JENA-366
> URL: https://issues.apache.org/jira/browse/JENA-366
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Fuseki 0.2.5
> Reporter: Priyaranjan
>
> Currently in FUSEKI we dont have an option to set UnionDefaultGraph while
> running SPARQL queries. Though we can set UnionDefaultGraph in the
> DatasetAssembler , but then it limits the user from specifying this option
> while querying.
> Is it possible to give the user an option to pass the value for
> UnionDefaultGraph in the FUSEKI UI , and set it to the context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
