On 24/06/2019 02:56, 刑天 wrote:
One Assembler per service. But the different service may point to the same
database
The UI does not have complete coverage of all possible reconfiguration
of services. To get a shared database, presumably there must have been
setup using configuration files.
At some point, it gets too complicated and it becomes a matter of using
the configuration files.
Fuseki Main is (by design) capable of having the configuration
manipulated - but it does not have a UI liek Fuseki/Webapp(Full) does.
For background- in what way are the two service setups for the same
database different?
Andy
At 2019-06-24 03:38:22, "Andy Seaborne" <[email protected]> wrote:
If you delete the dataset (via its service name), you are deleting the
database itself.
What's your setup? Do you have one assembler per service?
Andy
On 23/06/2019 15:59, 刑天 wrote:
I'm using fuseki to serve several datasets. And I'm using a style that two
assembler point to the same TDB directory with two different name and URL. When
I delete one dataset using fuseki delete dataset URL, the TDB directory delete
along. So this can problem that another dataset which point to the same TDB
directory fails. And this is the only API I can use to delete dataset without
shuting down the fuseki server. So I have no choice but wrote a new API which
only delete assembler file(besides one which only create dataset with specified
tdb path and other description). Is there another way to do these things? Am I
doing it right?
