refactor(triplestore): remove graphDB support (#2037)

* remove graphDB related scripts + clean docs * remove consistency checking * remove graphDB config * refactor twirl templates related to graphDB * remove embedded-jena-graphdb config * refactor twirl templates related to graphDB in admin routes * refactor twirl templates related to graphDB in v1 routes * remove GraphDBAPI * remove more graphDB inference related stuff * update docs * remove more graphDB stuff * PR changes * more PR changes * chore: release 20.1.0 (#2036) * commit to trigger bad gh actions Co-authored-by: DaSCH Bot <50987250+daschbot@users.noreply.github.com>
dasch-swiss · Apr 13, 2022 · bf17bca
1 parent 57d40f7
commit bf17bca
Show file tree

Hide file tree

Showing 251 changed files with 2,232 additions and 10,910 deletions.
diff --git a/README.md b/README.md
@@ -137,7 +137,7 @@ We write automated tests using [ScalaTest](https://www.scalatest.org). You can r
 
 There are three sets of automated tests:
 
-* Unit tests, route-to-route tests, and end-to-end tests are under `webapi/src/test`. To run these, type `graphdb:test` or `graphdb-free:test` (depending on which triplestore you're using) at the SBT console in the `webapi` project. To run a single test, use `graphdb:test-only *NameOfTestSpec`.
+* Unit tests, route-to-route tests, and end-to-end tests are under `webapi/src/test`. To run these, type `test` at the SBT console in the `webapi` project. To run a single test, use `testOnly *NameOfTestSpec`.
 * Integration tests, which can involve [Sipi](https://github.com/daschswiss/sipi), are under `src/it`. To run these, first start Sipi, then type `it:test` at the SBT console in the `webapi` project.
 
 Whenever you add a new feature or fix a bug, you should add one or more tests

diff --git a/docs/02-knora-ontologies/knora-base.md b/docs/02-knora-ontologies/knora-base.md
@@ -953,9 +953,6 @@ in user-created ontologies. Three types of consistency rules are enforced:
 - Constraints on the types of the subjects and objects of OWL object properties must be satisfied.
 - A datatype property may not have an empty string as an object.
 
-The implementation of consistency checking is partly triplestore-dependent; Knora may be able to provide stricter checks
-with some triplestores than with others.
-
 ### OWL Cardinalities
 
 As noted in [Resources](#resources), each subclass of

diff --git a/docs/04-publishing-deployment/configuration.md b/docs/04-publishing-deployment/configuration.md
@@ -53,10 +53,6 @@ A number of core settings is additionally configurable through system environmen
 | app.triplestore.use-https                                   | KNORA_WEBAPI_TRIPLESTORE_USE_HTTPS                              | false                |
 | app.triplestore.host                                        | KNORA_WEBAPI_TRIPLESTORE_HOST                                   | localhost            |
 | app.triplestore.auto-init                                   | KNORA_WEBAPI_TRIPLESTORE_AUTOINIT                               | false                |
-| app.triplestore.graphdb.port                                | KNORA_WEBAPI_TRIPLESTORE_GRAPHDB_PORT                           | 7200                 |
-| app.triplestore.graphdb.repository-name                     | KNORA_WEBAPI_TRIPLESTORE_GRAPHDB_REPOSITORY_NAME                | knora-test           |
-| app.triplestore.graphdb.username                            | KNORA_WEBAPI_TRIPLESTORE_GRAPHDB_USERNAME                       | admin                |
-| app.triplestore.graphdb.password                            | KNORA_WEBAPI_TRIPLESTORE_GRAPHDB_PASSWORD                       | root                 |
 | app.triplestore.fuseki.port                                 | KNORA_WEBAPI_TRIPLESTORE_FUSEKI_PORT                            | 3030                 |
 | app.triplestore.fuseki.repository-name                      | KNORA_WEBAPI_TRIPLESTORE_FUSEKI_REPOSITORY_NAME                 | knora-test           |
 | app.triplestore.fuseki.username                             | KNORA_WEBAPI_TRIPLESTORE_FUSEKI_USERNAME                        | admin                |

diff --git a/docs/04-publishing-deployment/getting-started.md b/docs/04-publishing-deployment/getting-started.md
@@ -50,9 +50,6 @@ DSP-API is designed to work with any standards-compliant
 triplestore. It is primarily tested with
 [Apache Jena Fuseki](https://jena.apache.org), an open source triplestore.
 
-Built-in support and configuration for a high-performance, proprietary
-triplestore [Ontotext GraphDB](http://ontotext.com/products/graphdb/) is
-provided but unmaintained (GraphDB must be licensed separately by the user).
 Other triplestores are planned.
 
 ## Running the DSP-Stack

diff --git a/docs/04-publishing-deployment/updates.md b/docs/04-publishing-deployment/updates.md
@@ -15,54 +15,7 @@ manual changes are needed, these will be described in the release notes, and mus
 done first.
 
 Before starting a new version of Knora, back up your repository, so you can restore it
-in case the automatic repository update fails. You can use one of these scripts
-in `webapi/scripts`:
-
-- `fuseki-dump-repository.sh` for Fuseki
-- `graphdb-dump-repository.sh` for GraphDB
-
+in case the automatic repository update fails. For Fuseki use `fuseki-dump-repository.sh`
+script located in `webapi/scripts`.
 
 For information on command-line options, run the script with no arguments.
-
-## Upgrading from a Knora Version Before 7.0.0
-
-**WARNING**: If you do not follow this procedure, your data may be
-corrupted, and Knora may not work.
-
-You must first upgrade to Knora 7.0.0, then upgrade again to the current
-version.
-
-The overall procedure is:
-
-1. Back up your repository as described above.
-
-2. Install Knora release 7.0.0, and read the general instructions in
-   `upgrade/graphdb-se/old/README.md` in that release.
-
-3. Follow the instructions in one of the subsections below for the version you are
-   upgrading from.
-
-4. Back up your repository again.
-
-5. Install the current release of Knore, and follow any manual update instructions
-   in its release notes.
-
-6. Start Knora to continue the automatic upgrade.
-
-### Upgrading from Knora 6.0.0 or 6.0.1
-
-1. Follow the instructions in `upgrade/graphdb-se/old/1263-knora-admin/README.md`.
-
-2. Follow the instructions in
-   [Upgrading from Knora 7.0.0 or Later](#upgrading-from-knora-7-0-0-or-later).
-
-### Upgrading from Knora 5.0.0 
-
-1. Follow the instructions in `upgrade/graphdb-se/old/1211-datetime/README.md`.
-
-2. Follow the instructions in `upgrade/graphdb-se/old/1230-delete-previews/README.md`.
-
-3. Follow the instructions in `upgrade/graphdb-se/old/1263-knora-admin/README.md`.
-
-4. Follow the instructions in
-   [Upgrading from Knora 7.0.0 or Later](#upgrading-from-knora-7-0-0-or-later).
diff --git a/docs/05-internals/design/api-v2/gravsearch.md b/docs/05-internals/design/api-v2/gravsearch.md
@@ -309,9 +309,7 @@ When the triplestore-specific version of the query is generated:
 
 Gravsearch also provides some virtual properties, which take advantage of forward-chaining inference
 as an optimisation if the triplestore provides it. For example, the virtual property
-`knora-api:standoffTagHasStartAncestor` is equivalent to `knora-base:standoffTagHasStartParent*`, but
-with GraphDB it is implemented using a custom inference rule (in `KnoraRules.pie`) and is therefore more
-efficient. If Knora is not using the triplestore's inference, `SparqlTransformer.transformStatementInWhereForNoInference`
+`knora-api:standoffTagHasStartAncestor` is equivalent to `knora-base:standoffTagHasStartParent*`. If Knora is not using the triplestore's inference, `SparqlTransformer.transformStatementInWhereForNoInference`
 replaces `knora-api:standoffTagHasStartAncestor` with `knora-base:standoffTagHasStartParent*`.
 
 # Optimisation of generated SPARQL

diff --git a/docs/05-internals/design/principles/consistency-checking.md b/docs/05-internals/design/principles/consistency-checking.md
@@ -5,6 +5,9 @@
 
 # Consistency Checking
 
+**Attention!** GraphDB is not supported anymore, therefore parts related 
+to it in this document are redundant.
+
 ## Requirements
 
 Knora is designed to prevent inconsistencies in RDF data,

diff --git a/docs/05-internals/design/principles/design-overview.md b/docs/05-internals/design/principles/design-overview.md
@@ -26,7 +26,7 @@ Knora is written in [Scala](http://www.scala-lang.org/), using the
 [Akka](http://akka.io/) framework for message-based concurrency. It is
 designed to work with any standards-compliant triplestore via
 the [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/), but is currently
-tested only with [Ontotext GraphDB](http://graphdb.ontotext.com/) (with support
+tested only with [Apache Jena Fuseki](https://jena.apache.org) (with support
 for other triplestores coming soon).
 
 ## Knora APIs

diff --git a/docs/05-internals/design/principles/store-module.md b/docs/05-internals/design/principles/store-module.md