The allows federated query of any number of graph dbs across any number of connections with any unique configurations per db desired (permissions, time-travel).
In order to query against any arbitrary set of graph dbs, you compose those dbs together using the new API dataset.
e.g. to compose these 3 dbs into a single dataset:
In this case, all the dbs are composed as a default graph, but they can still be targeted invidually for specific where statements using the graph function:
If you'd like to have only specific dbs part of the "default graph", you can supply the alias names as a list with a second argument to fluree/dataset:
The allows federated query of any number of graph dbs across any number of connections with any unique configurations per db desired (permissions, time-travel).
In order to query against any arbitrary set of graph dbs, you compose those dbs together using the new API
dataset
.e.g. to compose these 3 dbs into a single dataset:
In this case, all the dbs are composed as a default graph, but they can still be targeted invidually for specific where statements using the
graph
function:If you'd like to have only specific dbs part of the "default graph", you can supply the alias names as a list with a second argument to
fluree/dataset
:In this case, only
test/books
andtest/movies
would be part of the default graph.This closes issue: https://github.com/fluree/core/issues/96