Currently, federated queries are possible only against a single conn. The dbs that need to respond to the query (i.e. named via from or fromNamed) are loaded internally against that conn object.
Nexus currently has IPFS and non-IPFS (i.e. fs-based) datasets supported on separate conn instances. In order to enable federated queries with 2 conn instances, the APIs enabling federated query should support a dataset or list/vector/set of dbs
@zonotope may have additional comments about what, specifically, could or should change to enable this.
Once this work is complete, we will need to make a ticket for query-server / cloud-transactor to leverage this when handling federated queries (cc: @jakep36 @JaceRockman)
Description
Currently, federated queries are possible only against a single
conn
. Thedb
s that need to respond to the query (i.e. named viafrom
orfromNamed
) are loaded internally against thatconn
object.Nexus currently has IPFS and non-IPFS (i.e. fs-based) datasets supported on separate
conn
instances. In order to enable federated queries with 2conn
instances, the APIs enabling federated query should support adataset
or list/vector/set ofdb
s@zonotope may have additional comments about what, specifically, could or should change to enable this.