Con­figu­ration para­meter "$smwgEnabledFulltextSearch"

From semantic-mediawiki.org
Configuration parameter details:
Name $smwgEnabledFulltextSearch
Description Sets whether full-text search support for properties may be used
Default setting
false
(Other) available settings
true

Allows to enable full-text search for properties

Software Semantic MediaWiki
Since version
Until version still available
Configuration Full-text search · Experimental
Keyword full-text search · data store · relational database · sql store · sql database · experimental


$smwgEnabledFulltextSearch is a configuration parameter that sets whether full-text search support may be used. It is specific to a relational data store and currently supports MySQL/MariaDB1 and SQLite2 while PostgreSQL34 is currently not supported. It was introduced in Semantic MediaWiki 2.5.0Released on 14 March 2017 and compatible with MW 1.23.0 - 1.29.x..1

Using the feature connected to this configuration parameter is considered experimental!

Default setting[edit]

$smwgEnabledFulltextSearch = false;

This means that full-text search support is not available.

Changing the default setting[edit]

Maintenance script "rebuildFulltextSearchTable.php"Allows to rebuild the full text search data table has to be run after enabling this feature. Also set up a cron job to regularity run this maintenance script for best full-text search experience.

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

Enable the full-text search feature
$smwgEnabledFulltextSearch = true;

This means that full-text search support is available. The wiki will now store text elements using a separate table in order for the relational back-end to use special full-text index operations.

See also[edit]

General information
Related configuration parameters

References

  1. a b  Semantic MediaWiki: GitHub pull request gh:smw:1481
  2. ^  Semantic MediaWiki: GitHub pull request gh:smw:1801
  3. ^  Semantic MediaWiki: GitHub pull request gh:smw:1956
  4. ^  PostgreSQL is not supported due to a different index schema (e.g. to_tsvector, to_tsquery) but users interested to make it available are encouraged to have a look at the "MySQLValueMatchConditionBuilder" on how to create a PostgreSQL specific implementation.