This ticket is for the ability to manage the bigdata namespaces in the workbench.
This is a feature request for a JSP page that can be bundled with the WAR and also deployed standalone to a servlet container for the cluster. The JSP page will walk people through the configuration of a KB instance. For the standalone deployment, it might also
This actual configuration can be done programatically using the REST Multi-Tenancy API. The JSP page will, in effect, walk people through a decision tree to help them configure the database more easily.
Configuring a new KB instance is much easier to script than editing properties in an existing KB instance, or even than providing a description of the implications of those properties. Therefore, JSP page will focus on configuration of new KB instances. Note that both the standalone and clustered deployments allow multiple KB instances (multi-tenancy). The JSP page can be used to setup new KBs.
We also need to offer simple patterns to allow bulk loading into a KB following by incremental truth maintenance against that KB. My preference here is to add some options to the SPARQL UPDATE "LOAD" operation that allow loading data without truth maintenance into a KB for which truth maintenance is enabled. (The load needs to tunnel to the AbstractTripleStore or explicitly temporarily disable TM at the Sail layer). We would also need to offer a SPARQL UPDATE operation to force the database at once closure once some sequence of files had been loaded. The approach then needs to be documented on the wiki.