[
https://issues.apache.org/jira/browse/JENA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036221#comment-16036221
]
ASF GitHub Bot commented on JENA-1074:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/260
The PR keeps "find" operations on `DatasetGraph` returning
`Iterator<Quad>`. A graph is used for`Iterator<Triple>`.
The PR adds one new operation: `DatasetGraph.getUnionGraph()`.
The implementation in `DatasetGraphBase` uses `GraphUnionRead` which uses
`DatasetGraph.findNG(Quad.unionGraph, ?, ?, ?)`.
`Graph.find()` (no arguments) is added for convenience and to match
`DatasetGraph.find()`.
> 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.15#6346)
