It looks like it is HDT's responsibility - they provide the code to process
hdt:fileName.
Andy
(why not preprocess a template file to produce the instance specific
config.ttl as you move it around?)
On 19 October 2017 at 11:20, Rob Vesse <[email protected]> wrote:
> HDT is an external project which Jena itself does not support
>
> As described we can’t tell if the project is with Jena Fuseki or HDT, a
> stack trace and/or log output would be useful here to determine which is
> the case
>
> Rob
>
> On 19/10/2017 15:54, "Laura Morales" <[email protected]> wrote:
>
> Hi,
>
> I'm following this guide http://www.rdfhdt.org/manual-
> of-hdt-integration-with-jena/#fuseki to run a Fuseki server on top of HDT
> files. It works fine, but I have to move my config file around between
> several instances, and some graphs (HDT files) might not be available on
> some instances. Right now, if one HDT file is not available, Fuseki blows
> up with a "File not found" exception and the entire endpoint is unusable
> because of 1 missing file. Would it be possile, please..., to add a flag to
> Fuseki to simply ignore any HDT graph that has been defined in the config
> file, but the corresponding HDT is missing?
>
> Thank you very much!
>
>
>
>
>
>
