[
https://issues.apache.org/jira/browse/JENA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042779#comment-16042779
]
ASF subversion and git services commented on JENA-1074:
-------------------------------------------------------
Commit 462fe53a8fbac8770471251be676a050d29a4d1a in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=462fe53 ]
JENA-1074: Use DatasetGraph.findNG for dynamic union graph .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)
