working with jena/fuseki

[moissinac]

Expected Behavior

After installation and configuration, being capable to add a dataset

Actual Behavior

Adding a dataset by naming it and giving an access point always gives the message "There was no resource in the selected dataset! This might be due to the connection problems or because the estimated query execution time exceeds the configured limit. Please check the connection parameters of your dataset's Sparql endpoint or add resources to your dataset..." in the interface and the message Error in sample facet config creation update query: PREFIX ldr: https://github.com/ali1k/ld-reactor/blob/master/vocabulary/index.ttl# PREFIX rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# PREFIX rdfs: http://www.w3.org/2000/01/rdf-schema# PREFIX owl: http://www.w3.org/2002/07/owl#

        INSERT DATA {
         GRAPH <http://givingsense.eu/datamusee/ldreactorconfig> {
            <http://givingsense.eu/datamusee/ldreactorconfig/fcf1565444554> a ldr:FacetsConfig ;
                     ldr:dataset <http://givingsense.eu/datamusee/onto/d1565444553> ;
                      rdfs:label """test Facets Config""" ;
                     ldr:list rdf:type ;
                     ldr:createdOn "2019-08-10T13:42:33.717Z"^^xsd:dateTime;

                     ldr:config <http://ld-r.org/fpc1565444554> .
         }

        }

Please also check if the configuration SPARQL endpoint is running and is updateable ... in the console

Steps to Reproduce the Problem

Install ld-reactor, run it by typing npm run build:windows

Specifications

• Version: 1.3.7
• Platform: windows
• Subsystem:

Hypothesis

My configuration gives host: 'localhost', port: 3030, path: '/ldreactor/sparql', endpointType: 'fuseki' in server.js By lsreactor seems to try to update this default dataset and with fuseki, the update point is /ldreactor/update while the query point is either /ldreactor/query or /ldreactor/sparql So, it seems impossible to specify a different endpoint for query and for update.

[ali1k]

thanks for reporting this issue. By default there is no support for fuseki endpoints. Can you check https://github.com/ali1k/ld-r/blob/master/services/utils/helpers.js#L156 and see if fuseki API is similar to any of the existing APIs? If not, the best would be to make a PR that adds fuseki API.