You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently we can specify custom dataset for a sparql query with FROM and FROM NAMED declarations, whose default-graph is merge of graphs declared with FROM, and whose named graphs are individual named graphs declared with FROM NAMED.
This pattern works fine until we have to search among merge of small number of named graphs, by enumerating all of them with FROM. But if we have to search across merge of thousands of small named graphs (like those, trusted-by-an-authority, extracted-from-specific-resources, have-certain-provanence), then it won’t scale to mention all of those constituent graphs of custom default graph in every sparql query.
BlazeGraph allows for such virtual views through their support for Virtual Graphs.
@beebs-systap , @iansrobinson et al., Can support for virtual graphs which is there in blazegraph versions be available in neptune? It solves many practical problems. And seems easy to implement.
Thanks
Presently we can specify custom dataset for a sparql query with FROM and FROM NAMED declarations, whose default-graph is merge of graphs declared with FROM, and whose named graphs are individual named graphs declared with FROM NAMED.
This pattern works fine until we have to search among merge of small number of named graphs, by enumerating all of them with FROM. But if we have to search across merge of thousands of small named graphs (like those, trusted-by-an-authority, extracted-from-specific-resources, have-certain-provanence), then it won’t scale to mention all of those constituent graphs of custom default graph in every sparql query.
BlazeGraph allows for such virtual views through their support for Virtual Graphs.
And Virtuoso supports it through Graph Groups
Is there any possible way we can do this in neptune?
Thanks for your work.. @beebs-systap, @iansrobinson and all.
The text was updated successfully, but these errors were encountered: