Can you say a little more about your aims? Why do you want to put these graphs together? Do you want to write queries over their union? Where do the graphs come from? Do they partition the subjects of triples? (If they do, you don't need to use graphs to separate them.)
Using s-put (or any other HTTP technique) will have costs that depend on your local situation. If your client (say, s-put) is on the same machine as Fuseki, those costs might not be very much at all. If Fuseki is far away and across an unreliable network, those cost might be a lot. ajs6f > On Nov 26, 2017, at 1:12 PM, Laura Morales <[email protected]> wrote: > >> Instead use one TDB dataset and update one graph using s-put > > If I'm correct this works over HTTP; would this be a good fit for large > graphs as well (eg wikidata)? > The use case that I have in mind is "replace graph G from dataset D every > once in a while (week or month)", so I thought using a TDB2 store for each > graph in their own location was a good idea. Not different stores; all TDB2 > stores. Like this > > <#dataset> rdf:type ja:RDFDataset ; > ja:namedGraph > [ ja:graphName <http://example.org/name1> ; > ja:graph <#graph1> ] ; > > So I could just delete the graph folder and replace it with another directory > containing the new version of the graph created with tdb2.tdbloader.
