[ 
https://issues.apache.org/jira/browse/JENA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206731#comment-17206731
 ] 

Marco Neumann commented on JENA-1969:
-------------------------------------

Great Greg, this looks good. I can now start the server with the combination of 
-rf -t and -i.

One aspect we should considered is the message about empty datasets.

"DatasetOperations WARN  Datset empty. Spatial Index not constructed. Server 
will require restarting after adding data and any updates to build Spatial 
Index."

Could we not create an empty spatial index here to allow users start off with 
an empty dataset in tdb?


> Can't start geosparql fuseki server with -rf and -t
> ---------------------------------------------------
>
>                 Key: JENA-1969
>                 URL: https://issues.apache.org/jira/browse/JENA-1969
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki, Spatial, TDB
>    Affects Versions: Jena 3.16.0
>         Environment: Ubuntu 20.04.1 LTS
> JENA_HOME=/apache-jena-3.17.0-SNAPSHOT
> FUSEKI_HOME=/home/lotico/jena/apache-jena-fuseki-3.17.0-SNAPSHOT
> openjdk version "13.0.3" 2020-04-14
> OpenJDK Runtime Environment (build 13.0.3+3-Ubuntu-1ubuntu2)
> OpenJDK 64-Bit Server VM (build 13.0.3+3-Ubuntu-1ubuntu2, mixed mode)
>            Reporter: Marco Neumann
>            Assignee: Greg Albiston
>            Priority: Major
>             Fix For: Jena 3.17.0
>
>
> geosparql fuseki server can't be started with option combination -rf and -t 
> as described in the jena fuseki geosparql user documentation 
> (https://jena.apache.org/documentation/geosparql/geosparql-fuseki). 
> Individually with either option -rf or -t fuseki geosparql starts fine and 
> works as expected. Data can be loaded programmatically to tdb once created.
> {noformat}
> java -jar jena-fuseki-geosparql-3.17.0-20200915.115805-17.jar -rf data.ttl -t 
> "testDB2"
> WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will 
> impact performance.
> [2020-09-25 20:22:39] Main       INFO  Arguments Received: [-rf, data.ttl, 
> -t, testDB2]
> [2020-09-25 20:22:39] DatasetOperations INFO  Server Configuration: 
> port=3030, datsetName=ds, loopbackOnly=true, updateAllowed=false, 
> inference=false, applyDefaultGeometry=false, validateGeometryLiteral=false, 
> convertGeoPredicates=false, removeGeoPredicates=false, queryRewrite=true, 
> tdbFile=testDB2, fileGraphFormats=[FileGraphFormat{rdfFile=data.ttl, 
> graphName=, rdfFormat=Turtle/pretty}], fileGraphDelimiters=[], 
> indexEnabled=true, indexSizes=[-1, -1, -1], indexExpiries=[5000, 5000, 5000], 
> spatialIndexFile=null, help=false
> [2020-09-25 20:22:39] DatasetOperations INFO  TDB Dataset: testDB2
> [2020-09-25 20:22:41] DatasetOperations INFO  Reading RDF - Started - File: 
> data.ttl, Graph Name: , RDF Format: Turtle/pretty
> [2020-09-25 20:22:41] DatasetOperations INFO  Reading RDF - Completed - File: 
> data.ttl, Graph Name: , RDF Format: Turtle/pretty
> Exception in thread "main" 
> org.apache.jena.tdb.transaction.TDBTransactionException: Not in a transaction
>       at 
> org.apache.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:138)
>       at 
> org.apache.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:49)
>       at 
> org.apache.jena.sparql.core.DatasetGraphWrapper.getR(DatasetGraphWrapper.java:103)
>       at 
> org.apache.jena.sparql.core.DatasetGraphWrapper.isEmpty(DatasetGraphWrapper.java:192)
>       at org.apache.jena.sparql.core.DatasetImpl.isEmpty(DatasetImpl.java:247)
>       at 
> org.apache.jena.fuseki.geosparql.DatasetOperations.setup(DatasetOperations.java:95)
>       at org.apache.jena.fuseki.geosparql.Main.main(Main.java:64)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to