Why wouldn't you just load these as two separate datasets available at different endpoints in one instance of Fuseki? Why try to fool Fuseki into thinking that two datasets are really one?
ajs6f > On Nov 21, 2019, at 6:57 AM, Amandeep Srivastava > <[email protected]> wrote: > > Hi, > > Is there any resource that talks about caching in Fuseki service? > > Is is handled by Fuseki server itself or the TDB? (I'm using tdb dataset in > the backend as input) And can we disable the cache? > > My use case is to query two dumps, one old and one new and I'm setting - - > loc to a soft link pointing to the new dump while running fuseki. At times, > I wish to point my soft link to the older dump and query that. I don't want > to run another instance of the server. > > By understanding caching, I just want to make sure that when I point my > soft link to new location, fuseki service doesn't use its older cache to > answer incoming queries. > > Thanks, > Aman
