$ docker-compose logs fuseki Attaching to fuseki fuseki | WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance. fuseki | [2022-02-01 17:08:14] INFO Main :: Arguments Received: [-t, /fuseki/databases/DB2, --tdb2, --dataset, dst, --inference] fuseki | [2022-02-01 17:08:14] INFO DatasetOperations :: Server Configuration: port=3030, datsetName=dst, loopbackOnly=true, updateAllowed=false, inference=true, applyDefaultGeometry=false, validateGeometryLiteral=false, convertGeoPredicates=false, removeGeoPredicates=false, queryRewrite=true, tdbFile=/fuseki/databases/DB2, fileGraphFormats=[], fileGraphDelimiters=[], indexEnabled=true, indexSizes=[-1, -1, -1], indexExpiries=[5000, 5000, 5000], spatialIndexFile=null, tdb2=true, help=false fuseki | [2022-02-01 17:08:14] INFO DatasetOperations :: TDB Dataset: /fuseki/databases/DB2, TDB2: true fuseki | [2022-02-01 17:08:15] INFO GeoSPARQLOperations :: Applying GeoSPARQL Schema - Started fuseki | [2022-02-01 17:08:15] INFO GeoSPARQLOperations :: GeoSPARQL schema not applied to empty graph: default
Op di 1 feb. 2022 om 18:13 schreef Erik Bijsterbosch < e.bijsterbo...@gmail.com>: > Hi all, > > I created a new jena tdb2 database and loaded it with 256 million triples > in a named graph, using a fuseki2/tdb2 4.3.2 docker setup. > The data also consist of geometries so I built a new docker image based > on jena-fuseki-geosparql 4.3.2 > When I bring up the new fuseki container it seems I can't address the > named graph reusing the tdb2 database, it searches through the default > graph. > According to the --help graph names can only be provided when loading from > files or is there another way? > > Regards, > Erik >
