$smwgDefaultStore

Configuration parameter details:
Name	$smwgDefaultStore
Description	Sets the storage backend to be used for the semantic data
Default setting	SMWSQLStore3
(Other) available settings	SMWSparqlStore Allows to set the usage of a RDF database to be used for the semantic data SMWElasticStore Allows to set the usage of a Elasticsearch database to be used for the semantic data
Software	Semantic MediaWiki
Since version	0.7
Until version	still available
Configuration	Installation · Store settings
Keyword	sqlstore · sparqlstore · store · sparql · sql · elasticsearch · elasticsearchstore

$smwgDefaultStore is a configuration parameter that is used to set the storage backend for the semantic data either SQL, SPARQL or Elasticsearch. This configuration parameter was introduced in Semantic MediaWiki 0.7Released on 28 April 2007 and compatible with MW 1.8.x - 1.10.x..

From Semantic MediaWiki 1.2.0Released on 10 July 2008 and compatible with MW 1.11.x - 1.14.x. to Semantic MediaWiki 1.7.1Released on 5 March 2012 and compatible with MW 1.16.0 - 1.19.x. the default store was SMWSQLStore2 (relational database) which received legacy support in Semantic MediaWiki 1.8.0Released on 2 December 2012 and compatible with MW 1.17.0 - 1.22.x
(except 1.22.1). and was dropped with Semantic MediaWiki 1.9.0Released on 3 January 2014 and compatible with MW 1.19.0 - 1.22.x..

Default setting

$smwgDefaultStore = 'SMWSQLStore3';

This means that a relational database is being used as a data backend/store for Semantic MediaWiki which is suitable for most standard environments.

Available options

• SMWSQLStore3 − Sets a relational database as a data backend/store, i.e. MySQL, SQLite or PostgreSQL

  Note: This option is available since Semantic MediaWiki 1.8.0Released on 2 December 2012 and compatible with MW 1.17.0 - 1.22.x
(except 1.22.1)..

• SMWSparqlStore − Sets a sparql database as the data backend/store, e.g. Blazegraph, Sesame, Fuseki etc.

  Note: This option is available since Semantic MediaWiki 1.6.0Released on 30 July 2011 and compatible with MW 1.15.x - 1.18.x..

• SMWElasticStore − Sets an Elasticsearch database as the data backend/store

  Note: This option is available since Semantic MediaWiki 3.0.0Released on 11 October 2018 and compatible with MW 1.27.0 - 1.31.x..

When choosing SMWElasticStore as as setting to this configuration parameter you still need a relational database providing data storage functionality. This is not the case for the other two available options.

Changing the default setting

To modify the setting to this configuration parameter, add one of the following lines to your "LocalSettings.php" file after the enableSemantics() call:

Change to a sparql database for data storage

$smwgDefaultStore = 'SMWSparqlStore';

See the help page on using SPARQL and RDF stores and the configuration parameter $smwgSparqlRepositoryConnectorIdentifies a database connector that ought to be used together with the semantic data store. for Semantic MediaWiki 2.0.0Released on 4 August 2014 and compatible with MW 1.19.0 - 1.24.x. and later for more information on this setting.

If you change the setting for this configuration parameter, please ensure to run maintenance script "setupStore.php"Allows to set up the data backend/store followed by maintenance script "rebuildData.php"Allows to rebuild all the semantic data for a selected data backend/store.

Change to a Elasticsearch database for data storage

$smwgDefaultStore = 'SMWElasticStore';

See the help page on using the Elasticsearch store for more information on this setting.1

If you change the setting for this configuration parameter, please ensure to run maintenance script "setupStore.php"Allows to set up the data backend/store followed by maintenance script "rebuildElasticIndex.php"Allows to rebuild all the semantic data for the Elasticsearch index.

See also

• Help page on database privileges, when using SMWSQLStore3
• Help page on using SPARQL and RDF stores
• Help page on using the Elasticsearch store
• Help page on configuration parameter $smwgQuerySourcesSets a list of sources, i.e. query back-ends that can return query results