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