On 21/11/2019 17:16, ajs6f wrote:
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?
Agreed.
ajs6f
On Nov 21, 2019, at 6:57 AM, Amandeep Srivastava
<amandeep.srivastava1...@gmail.com> 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.
In effect, symbolic links are resolved at he start and never checked again.
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.
You can't manipulate the file system going underneath Fuseki or TDB.
Mostly, likely it simply won't notice (the file are already open) but it
may be worse.
If you want to swap datasets in-place you'll need to stop and restart
Fuseki.
One different way is to use a reverse proxy (httpd for example) and have
two Fuseki servers. Switchover in the reverse proxy - they usually
reload configs while running, preserving oustanding requests.
Andy
Thanks,
Aman
