The name of the backend is virtuosobackend
. Thus, to use it one simply has to load it as follows:
const Soprano::Backend* virtBack = Soprano::PluginManager::instance()->discoverBackendByName("virtuosobackend");
indexes
- A comma separated list of quadruple indexes to be used (Example: 'spog
,posg
,opsg'
). If not specified, the indexes are not changed, ie. the Virtuoso defaults are used.fulltextindex
- Enable or disable the full text index which allows to perform full text queries on string literals embedded in SPARQL queries. For more information see the documentation on Virtuoso SPARQL extensions.none
- disable the indexsync
- enable syncroneous updates of the index (the index is always in sync. This might give a performace penalty)N
- The interval in minutes after which the index will be updated.NumberOfBuffers
- The number of buffers (8k in size) to be used by Virtuoso. Defaults to 2000.ServerThreads
- The number of server threads. Defaults to 100.CheckpointInterval
- The interval in minutes at which Virtuoso will automatically make a database checkpoint. Defaults to 60.MinAutoCheckpointSize
- The minimum size of the Virtuoso transaction log. An automatic checkpoint will not be made if there is less than MinAutoCheckpointSize bytes in the current transaction log. Defaults to 4000000.forcedstart
- A boolean property which when set will result in the backend killing any Virtuoso instance accessing the data in the storage dir before starting its own instance. This option is ignored when connecting to an already running Virtuoso server.The settings above are user settings and have to be provided using Soprano::BackendOptionUser:
Soprano::BackendSettings settings; // configure the used indexes settings << Soprano::BackendSetting( "indexes", "spog,posg,opsg" ); // set the full text index to be updated every 10 minutes settings << Soprano::BackendSetting( "fulltextindex", "10" );
The following setting is required for starting a local instance of Virtuoso:
This means that a conversion needs to take place whenever the empty graph or the special graph are encountered. This introduces a slight performance penalty. In the future an option might be introduced to disable this behaviour.
The backend does solve this issue for boolean values only by introducing a fake datatype for boolean literals. This is converted internally so the user of the backend will never notice it. The only exception may be queries that contain filters. More input is needed here.