Class DatabaseOptions
- All Implemented Interfaces:
MetaPropertyProvider
Non-structural database options. These options, unlike IndexOptions, are not
relevant to reading or creating the database. This set of options is for controlling behavior of the database as it
lives within a Stardog DBMS.
- Since:
- 0.7
- Author:
- Michael Grove, Evren Sirin, Edgar Rodriguez-Diaz, Fernando Hernandez
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic enumstatic enumDifferent types of datatype normalization algorithms supported by Stardog.static enumDifferent types of transaction isolation supported by Stardog. -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final ConfigProperty<Collection<String>> The name of one or more database archetypes, used to associate ontologies and constraints with new databases.static final ConfigProperty<Boolean> static final ConfigProperty<String> static final ConfigProperty<String> static final ConfigProperty<Boolean> static final ConfigProperty<Duration> The amount of time a connection to the database can be open, but inactive, before being automatically closed to reclaim the resources.static final InfoProperty<DateTime> Creation time of the database.static final InfoProperty<Long> The transaction ID at which this DB was created.static final InfoProperty<String> Creator of the database.static final longDefault offline timeout (in ms)static final ConfigProperty<Boolean> Option for enabling edge properties that allows RDF statements to appear as subjects of RDF statements (aka RDF*).static final ConfigProperty<com.complexible.stardog.index.EqualityReasoningLevel> static final ConfigProperty<Boolean> Controls whether query evaluation will use extended literal comparison (true, the default).static final ConfigProperty<Boolean> Internal signaling property, if the database failed to initialize.static final ConfigProperty<Boolean> static final ConfigProperty<Boolean> Ignore file errors while doing a bulk loadstatic final ConfigProperty<DatabaseOptions.InlineStoredQuery> static final ConfigProperty<List<IRI>> static final ConfigProperty<DatabaseOptions.LanguageNormalization> Configuration option for determining the normalization algorithm for the language tags of literals.static final ConfigProperty<Collection<String>> static final ConfigProperty<Collection<String>> static final ConfigProperty<Boolean> Option to enable memory-mapping in lucene indices (e.g., search, spatial).static final ConfigProperty<Boolean> static final InfoProperty<DateTime> Last modification time for the database.static final ConfigProperty<String> Name of the database.static final ConfigProperty<Collection<Namespace>> The default namespaces for the database.static final ConfigProperty<Duration> static final ConfigProperty<Boolean> Option for whether or not the database is online.static final Stringstatic final StringAny metadata property whose name starts with this prefix will be propagated to the parser.static final Map<MetaProperty<?>, Option<?>> Mapping of database options to correspondingparser options.static final ConfigProperty<Boolean> This option controls if the parser should preserve bnode identifiers specified in the source.static final ConfigProperty<Boolean> When enabled, the progress of various tasks will be printed in the server log.static final ConfigProperty<Boolean> This option controls the behavior for answering queries that don't specify a dataset (FROM or FROM NAMED) in the query.static final ConfigProperty<String> Option to set the default DESCRIBE query strategy for the database.static final ConfigProperty<Long> Configuration option for the max number of entries in the query-local dictionary before a persistent data structure is used (which can spill data to disk).static final ConfigProperty<Boolean> static final ConfigProperty<Boolean> Config option to enable or disable the query logging on a per database level.static final ConfigProperty<String> Configuration option for determining the memory limit used by query;static final ConfigProperty<com.complexible.stardog.QueryMemoryExceedsStrategy> Configuration option for determining strategy for the query behaviour once memory limit @{#OPTION_QUERY_MM_MEMORY_LIMIT} reached;static final ConfigProperty<QueryPlanReuse> This option determines how Stardog will reuse cached query plans.static final ConfigProperty<Duration> Determines max execution time for read query evaluation.static final ConfigProperty<Boolean> Configuration option for determining the update procedure that will be used for SPARQL update queries ADD, COPY and MOVE.static final ConfigProperty<Duration> Determines max execution time for SPARQL update query evaluation.static final ConfigProperty<Integer> static final ConfigProperty<String> static final ConfigProperty<Long> static final ConfigProperty<IRI> Option for the named graph which stores BI/SQL schema mappingstatic final ConfigProperty<Boolean> Controls whether Stardog parses RDF strictly (true, the default) or loosely (false)static final ConfigProperty<Collection<String>> static final ConfigProperty<DatabaseOptions.TransactionIsolation> Configuration option for setting the isolation level for transactions.static final ConfigProperty<Boolean> Option for whether or not the database logs all transactions events to disk.static final ConfigProperty<Integer> Number of statements per chunk when writing to the transaction log.static final ConfigProperty<Boolean> WhenTRANSACTION_LOGGINGis true andTRANSACTION_LOGGING_ROTATION_REMOVEis false, this option controls whether we keep backups of the rotated log file.static final ConfigProperty<Boolean> WhenTRANSACTION_LOGGINGis true, this option is for whether the rotated log will be kept or removed.static final ConfigProperty<String> Option for the max size for logged transactions on disk.static final ConfigProperty<Boolean> Option for whether or not the synchronization process should use rotated log during synchronization in Cluster mode.static final ConfigProperty<Boolean> static final ConfigProperty<String> Type of the database.static final ConfigProperty<Boolean> Option for whether to include virtual graphs for graph variable queries.static final ConfigProperty<Boolean> Config option to enable or disable the Voicebox AI features on a per database level.static final ConfigProperty<Collection<String>> static final ConfigProperty<Integer> static final ConfigProperty<Boolean> static final ConfigProperty<Collection<String>> -
Method Summary
Modifier and TypeMethodDescriptionstatic <T> voidcopyOption(Metadata theMetadata, MetaProperty<T> theProp, Options theOptions, Option<T> theOption) Copies one option from the metadata to the options if it already does not exist in the options.static voidcopyParserOptions(Metadata theMetadata, Options theOptions) Copies parser properties from the metadata to the options.static Metadatastatic OptionsgetParserConfig(Metadata theMetadata) Creates aparser configwith the given options.static OptionsgetParserOptions(Metadata theMetadata) Extracts theparser optionsfrom the metadata.
-
Field Details
-
OPTION_QUERY_LOG_ENABLED
- See Also:
-
NATIVE_METRICS_REPORTING_INTERVAL
-
EQUALITY_REASONING
public static final ConfigProperty<com.complexible.stardog.index.EqualityReasoningLevel> EQUALITY_REASONING -
CATALOG_SCHEMA_EXPORT
-
AUTO_SCHEMA_REASONING
-
STRICT_PARSING
Controls whether Stardog parses RDF strictly (true, the default) or loosely (false) -
EXTENDED_COMPARISON
Controls whether query evaluation will use extended literal comparison (
true, the default). The SPARQL spec does not define an ordering relationship between literals of different types (Section 15.1 ORDER BY) and equality check between two literals will produce a type error if the literals are not same (Section 17.4.1.7 RDFterm-equal). This results in unintuitive results such as the expression"123"^^xsd:int != "ABC"evaluating tofalse. Stardog extends the'<'operator (17.3.1 Operator Extensibility) such that literals of different datatypes are first compared based on their string values and then based on the string value of their datatypes. If this option is disabled literal comparison will be done as to produce type errors. -
PRESERVE_BNODE_IDS
This option controls if the parser should preserve bnode identifiers specified in the source. Preserving bnode identifiers help speed parsing and loading time but it also has an important side-effect that if two distinct files using the same bnode identifier are loaded to the same database, the bnode in different files will end up pointing to the same node in the database. If the input files do not use bnode identifiers (e.g. in Turtle syntax only [] are used for bnodes) then this configuration option has no effect since such bnodes are always assigned a unique identifier. But if input files use explicit bnode identifiers (e.g. _:bnode1 in Turtle syntax) and multiple files may use same bnode identifiers then this configuration option should be turned off.Default value: true
-
NAME
Name of the database. -
CREATOR
Creator of the database. -
TYPE
Type of the database. -
IGNORE_BULK_LOAD_FILE_ERRORS
Ignore file errors while doing a bulk load -
BULK_LOAD_STREAM_FACTORY
-
BULK_LOAD_STREAM_ARGS
-
CREATION_TX
The transaction ID at which this DB was created. Default should be null. -
CREATION_TIME
Creation time of the database. -
MODIFICATION_TIME
Last modification time for the database. -
TRANSACTION_LOGGING
Option for whether or not the database logs all transactions events to disk. When a database is created in Cluster mode, the default will be true. -
TRANSACTION_LOGGING_USE_ROTATED
Option for whether or not the synchronization process should use rotated log during synchronization in Cluster mode. -
VIRTUAL_TRANSPARENCY
Option for whether to include virtual graphs for graph variable queries. The default is false. -
LOCAL_IRI_TEMPLATE_INCLUDES
-
LOCAL_IRI_TEMPLATE_EXCLUDES
-
EDGE_PROPERTIES
Option for enabling edge properties that allows RDF statements to appear as subjects of RDF statements (aka RDF*). The default is false. -
TRANSACTION_LOGGING_ROTATION_SIZE
Option for the max size for logged transactions on disk. It has no effect withoutTRANSACTION_LOGGING. WhenTRANSACTION_LOGGING_USE_ROTATEDis enabled, total disk usage can be up to twice this value since both the active log and the rotated log are capped at this limit.- See Also:
-
TRANSACTION_LOGGING_ROTATION_REMOVE
WhenTRANSACTION_LOGGINGis true, this option is for whether the rotated log will be kept or removed.- See Also:
-
TRANSACTION_LOGGING_KEEP_ROTATED_BACKUP_FILES
WhenTRANSACTION_LOGGINGis true andTRANSACTION_LOGGING_ROTATION_REMOVEis false, this option controls whether we keep backups of the rotated log file. By default, we do not maintain backups since we could fill up the disk with backup files.- See Also:
-
TRANSACTION_LOGGING_CHUNK_SIZE
Number of statements per chunk when writing to the transaction log. Chunking allows small transactions to interleave with large ones.- See Also:
-
ONLINE
Option for whether or not the database is online. The value for this option at database creation time determines the initial state of the database. This option cannot be modified directly after the database has been created. The special admin functions should be used to change the value of this option. -
FAILED_INITIALIZE
Internal signaling property, if the database failed to initialize. -
QUERY_ALL_GRAPHS
This option controls the behavior for answering queries that don't specify a dataset (FROM or FROM NAMED) in the query. In such cases, the SPARQL specification says that the query should be answered only using the information in default graph (no context). However, sometimes it is desirable to answer such queries using all the information in the database including the default graph and all named graphs. Setting this option to true changes the behavior of Stardog to do this. The queries that specify a dataset are not affected by this option.
-
QUERY_PLAN_REUSE
This option determines how Stardog will reuse cached query plans. See
QueryPlanReusefor more details. -
NAMESPACES
The default namespaces for the database. Legal input is a comma-separated list of <prefix>=<namespace> values. -
CONNECTION_TIMEOUT
The amount of time a connection to the database can be open, but inactive, before being automatically closed to reclaim the resources. -
QUERY_TIMEOUT
Determines max execution time for read query evaluation. -
QUERY_UPDATE_TIMEOUT
Determines max execution time for SPARQL update query evaluation. -
ARCHETYPES
The name of one or more database archetypes, used to associate ontologies and constraints with new databases. Built-in archetypes are "PROV" and "SKOS", see the docs for instructions to create your own. -
LUCENE_MMAP
Option to enable memory-mapping in lucene indices (e.g., search, spatial). Memory mapping is enabled by default. -
QUERY_DESCRIBE_STRATEGY
Option to set the default DESCRIBE query strategy for the database. Built-in strategies include "default", "cbd" and "bidirectional. -
QUERY_EQUALITY_IDENTITY
-
TRANSACTION_ISOLATION
Configuration option for setting the isolation level for transactions.- See Also:
-
LANGUAGE_NORMALIZATION
Configuration option for determining the normalization algorithm for the language tags of literals. -
PROGRESS_MONITOR_ENABLED
When enabled, the progress of various tasks will be printed in the server log. -
QUERY_UPDATE_GRAPH_DIFF
Configuration option for determining the update procedure that will be used for SPARQL update queries ADD, COPY and MOVE. By default, Stardog will compute the diff between the source and the destination graphs and only apply the diff to the destination graph. -
QUERY_MEMORY_LIMIT
Configuration option for determining the memory limit used by query; -
QUERY_MM_EXCEEDS_STRATEGY
public static final ConfigProperty<com.complexible.stardog.QueryMemoryExceedsStrategy> QUERY_MM_EXCEEDS_STRATEGYConfiguration option for determining strategy for the query behaviour once memory limit @{#OPTION_QUERY_MM_MEMORY_LIMIT} reached; -
QUERY_LOG_ENABLED
Config option to enable or disable the query logging on a per database level. Only relevant in conjunction with the query log module. -
QUERY_DICTIONARY_SIZE_THRESHOLD
Configuration option for the max number of entries in the query-local dictionary before a persistent data structure is used (which can spill data to disk). The default value is 100K. -
GRAPH_ALIASES
-
SPARQL_SERVICE_RESULT_LIMIT
-
SERVICE_PREFETCH_THRESHOLD
-
SPARQL_SERVICE_CREDENTIALS_PASSTHROUGH_REGEX
-
TX_COMMIT_2P
-
INLINE_STORED_QUERY
-
LABEL_PROPERTIES
-
MEDIA_ENABLED
-
VOICEBOX_ENABLED
Config option to enable or disable the Voicebox AI features on a per database level. -
VOICEBOX_OPTIMIZE
-
VOICEBOX_PREPROCESORS
-
VOICEBOX_EXAMPLE_QUESTIONS
-
VOICEBOX_MAX_SCHEMA_SIZE
-
SQL_SCHEMA_GRAPH
Option for the named graph which stores BI/SQL schema mapping -
SYSTEM_GRAPHS
-
DEFAULT_OFFLINE_TIMEOUT
public static final long DEFAULT_OFFLINE_TIMEOUTDefault offline timeout (in ms) -
PARSER_OPTION_PREFIX
Any metadata property whose name starts with this prefix will be propagated to the parser.- See Also:
-
PARSER_OPTIONS
Mapping of database options to correspondingparser options.
-
-
Method Details
-
defaults
-
getParserOptions
Extracts theparser optionsfrom the metadata. -
copyParserOptions
Copies parser properties from the metadata to the options. Parser properties are thoseexplicitly enumeratedas well as those whose name starts withPARSER_OPTION_PREFIX. Options that already exist will not be overwritten. -
copyOption
public static <T> void copyOption(Metadata theMetadata, MetaProperty<T> theProp, Options theOptions, Option<T> theOption) Copies one option from the metadata to the options if it already does not exist in the options. -
getParserConfig
Creates aparser configwith the given options.
-