[
https://issues.apache.org/jira/browse/JENA-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005944#comment-15005944
]
A. Soroka edited comment on JENA-1064 at 11/15/15 3:43 PM:
-----------------------------------------------------------
I did not realize that part of the {{find}} contract is that kind of
repeatability. By luck, my recent PR for JENA-624 fulfills that, but I didn't
plan for it. In any event +1 to returning triples. That seems to me to be
really what the "find in union" operation is about: discarding graph-node
information, almost a kind of forgetful functor.
was (Author: ajs6f):
I did not realize that part of the {{find}} contract is that kind of
repeatability. By luck, my recent PR for JENA-624 fulfills that, but I didn't
plan for it. In any event +1 to returning triples. That seems to me to be
really what the "find in union" operation is about: discarding graph
information, almost a kind of forgetful functor.
> Add DatasetGraphBaseFind.findInUnionGraph
> -----------------------------------------
>
> Key: JENA-1064
> URL: https://issues.apache.org/jira/browse/JENA-1064
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> Add operation {{DatasetGraphBaseFind.findInUnionGraph}} so that
> implementations can be told explicitly when a union graph access is being
> done. This maybe the computed default graph or an explicit name of
> {{Quad.unionGraph}} i.e. {{<urn:x-arq:UnionGraph>}}. By the time it gets to
> this level, it is with a graph node name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
