Hi all, reading the TDB assembler doc [1], I was wondering how easy/difficult it would be to support multiple ja:graph for a ja:namedGraph, so that a large graph such as Wikidata could potentially be split into smaller graphs. Alternatively, since SPARQL supports multiple FROM instructions, there could be an option to configure "aliases" so that if the user writes "FROM <wikidata>" this will be translated to "FROM <wikidata-store1> <wikidata-store2> ..." where each <wikidata-storeN> is its own ja:namedGraph.
I think this could be equivalent to tdb:unionDefaultGraph, but instead of being a union among *all* graphs, only a union among a limited selection of graphs. It kinda sounds easy in theory, since it seems like a particular case of tdb:unionDefaultGraph, but... I don't know in practice if this would be possible? [1] https://jena.apache.org/documentation/tdb/assembler.html
