[
https://issues.apache.org/jira/browse/JENA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378143#comment-15378143
]
Andy Seaborne commented on JENA-1074:
-------------------------------------
JENA-1158
Union graph should work everywhere now.
Quads in the union graph would have to be created on-the-fly - returning the
underlying quads with the originating graph might make for unstable results
(different graph name from call to call).
So anything {{Iterator<Quad>}} is not so useful.
That leaves {{DatasetGraph.getUnionGraph()}} as a shorthand for
{{DatasetGraph.getGraph(Quad.unionGraph)}}.
{{GraphOps.unionGraph}} is available but hard to find ({{GraphOps}} is internal
really).
NB The union graph is read-only.
> Add find operations for DatasetGraph for the union graph.
> ---------------------------------------------------------
>
> Key: JENA-1074
> URL: https://issues.apache.org/jira/browse/JENA-1074
> Project: Apache Jena
> Issue Type: Brainstorming
> Components: ARQ
> Affects Versions: Jena 3.0.0
> Reporter: Andy Seaborne
> Priority: Minor
>
> (This follows on from JENA-1064)
> {{DatasetGraphBaseFind}} now has a {{find}} operations for the union graph
> added to make implementation easier.
> Should operation(s) be exposed in the core interface {{DatasetGraph}} (the
> application contract)? If so, how?
> The operations to consider include:
> * {{findInUnionGraph}} ({{Iterator<Triple>}})
> * {{findQuadsInUnionGraph}} ({{Iterator<Quad>}})
> * {{findInDftGraph}} ({{Iterator<Quad>}} - inconsistent naming with above)
> At the moment {{findInDftGraph}} returns quads and documents
> {{DatasetGraph.getDefaultGraph().find()}} as being the way to get triples.
> This suggests a different style where {{DatasetGraph}} has:
> * {{DatasetGraph.getUnionGraph()}}
> * {{DatasetGraphFind.findInUnionGraph}} ({{Iterator<Quad>}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
