Hi Andy,

Thanks for your quick response.

I followed your advice and now I'm able to access /$/ping and /$/stats
endpoints after running Fuseki with dcmd "fuseki" --port 3031 --conf
config.ttl --ping --stats

I can use the /$/stats instead of /$/datasets because what I need is just a
list of datasets. We are planning to use it with Zookeper for a production
HA solution. The initial testing looks great - but our infra/DevOps team
needed this /$/ping endpoint badly for Kubernetes deployment.

Cheers,
Piotr



pon., 3 sie 2020 o 16:25 Andy Seaborne <[email protected]> napisaƂ(a):

> The Fuseki integration is based on jena-fuseki-main, the non-webapp
> version of Fuseki.
>
> It is configured using the command line and a configuration file.
>
> "/$/ping" should be there if started with "--ping".
>
> It does not have the admin interface for addign/removing datasets.
>
> It does have (with "--stats") "/$/stats" which contains the dataset
> information and more in a different way.
>
>      Andy
>
> On 03/08/2020 13:15, Piotr Nowara wrote:
> > Hi,
> >
> > I'm not able to issue any Admin Protocol endpoint call. I'm getting 404
> > each time. I need /$/ping and /$/datasets. Do I need to set up something
> > special for them? I've tried with a standalone RDF Delta (configured as
> > described in the tutorial) and also with the Zookeeper.
> >
> > Thanks,
> > Piotr
> >
>

Reply via email to