On 12/06/2019 20:07, Laura Morales wrote:
The reason why I would like to be able to do this, instead of merging one
dataset into another, is simply because the two datasets come from different
origins.
With an overlap of named graphs?
Potentially yes, but for my particular case I can work around it by renaming my
graphs if it makes any difference.
I've done a quick test using your assembler with ja:UnionModel, and using 2 TDB
datasets that I've created like this: tdbloader2 --loc dataset-1 data.nt (data.nt
contains only 1 unnamed graph). SELECT..WHERE queries return an empty results set,
but it *does* seem to work if I remove the tdb:graphName <urn:x-arq:UnionGraph>
properties.
And presumable turned on union mode.
<urn:x-arq:UnionGraph> is the union model and means the dtabases don't
need tdb:unionDefaultGraph
Where can I find more documentation about ja:UnionModel?
Its a bit cryptic TBH:
https://jena.apache.org/documentation/assembler/assembler-howto.html#union-models
A union dataset would be better but there is no assembler as Adam said.
I've never used it before and I don't really understand what's going on...
It creates an in-memory stateless union model.
Union models (which are used a lot in OWL) calculate the
graph-union-find over several submodels.
Classes UnionModelAssembler and MultiUnion.
PS: this only works with TDB1 right? Any way to make it work with TDB2?
No. Works for anything and mixtures:
Change the tdb:GraphTDB and tdb:DatasetTDB
to tdb2:GraphTDB2 and tdb2:DatasetTDB2
