Project items
Beginning to think about Jena 3.17.0, here are there are some project discussion points and a couple of development issues. == Surveys We could conduct some simple surveys on users@. I doubt we'd get a lot of feedback but some is better than none. 2 possibilities: ** Inference and scale: what inference do people actually use / want to use at scale? RDFS? SHACL rules? SKOS broader/narrower? This is triggered by a segment of the BOF session at AapcheCon2020 - as scale of data goes up, expressivity has to go down for performance tradeoffs if apps want query times that are compatible with UI. I having been wondering about a custom (java) RDFS engine for TDB that does subclass/subproperty/range/domain but not the axioms. This would be as well as the more expressive and complete Jena/rules. ** Java8 - Java11 evolution Try to understand the reasons why anyone is running on a Java8 runtime yet still upgrades Jena. == Rename the default branch to "main" Changing the name of the default branch for 'jena' and 'jena-site'. It causes us a small amount of work; it'll probably take some work from INFRA and forked repos will be affected. It can be done in stages - create the "main" off of the default so both exist for a sort while as we communicate the change. I've converted some of my other repos using instructions on the web and have had no issues. == JSON-LD There are some JSON-LD tickets. I don't have much to do with JSON-LD now and for the foreseeable future. Getting into the details of JSON-LD processing is unlikely for a while. I don't know if the issues are jena or upstream in jsonld-java. I've added a category for JSON-LD to make them more easily findable in JIRA. jena-osgi Information: On Java15 and 16, the build fails because Felix fails (actually downstream of Felix in BND) There is a fix in the downstream which will arrive sometime with Felix upgrade. It is the build, not Jena that is causing the error. The jobs are now set to -Pdev so we at least are running that part of Jena through these java versions. These "canary" jobs, and running once day. (We might as well use @weekly - these jobs are "as well as" running for the LTS java.)
[DRAFT] Apache Jena report (October 2020)
## Description: The mission of Jena is the creation and maintenance of software related to Java framework for building Semantic Web applications ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Jena was founded 2012-04-18 (8 years ago) There are currently 18 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 9:7. Community changes, past quarter: - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. - No new committers. Last addition was Greg Albiston on 2019-07-08. ## Project Activity: Jena usually does a release every 3-4 months. As noted last report, 3.15.0 has a problem with one of the server binaries, and new users have ran into problems. The project released 3.16.0 with a fix in July; user email and StackOverflow questions about the issue have dropped off. ## Community Health: The original Jena project (pre-ASF) celebrated it's 20th birthday! The first public release of code was 28th August 2000. We held a community event online, kindly hosted by the Lotico meetup, to mark the occasion. Claude Warren (PMC) organised a successful Jena track at ApacheCon with talks about Jena itself and from project using Jena. While the statistics show a reduction in activity and emails, a dip in the northern hemisphere summer is not unusual. The number of outstanding JIRA has increased slightly, by about 5 tickets.
[jira] [Commented] (JENA-1969) Can't start geosparql fuseki server with -rf and -t
[
https://issues.apache.org/jira/browse/JENA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206750#comment-17206750
]
Marco Neumann commented on JENA-1969:
-
also in addition we had a request at ApacheCon 2020 for TDB2 support in
geosparql-fuseki e.g. the ability to flag -t2 in the command line.
In the long term we might want to considers to go for a file (.ttl) based
configurable geosparql fuseki option here. but for now -t2 would suffice.
> 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)
[jira] [Commented] (JENA-1969) Can't start geosparql fuseki server with -rf and -t
[
https://issues.apache.org/jira/browse/JENA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Resolved] (JENA-1969) Can't start geosparql fuseki server with -rf and -t
[
https://issues.apache.org/jira/browse/JENA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Albiston resolved JENA-1969.
-
Fix Version/s: Jena 3.17.0
Resolution: Fixed
TDB now requires a transaction to check if dataset is empty. Transaction now
added.
> 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)
