The available configuration options for a Data Source depend on the type of the Data Source. Supported Data Source types include JDBC, MongoDB, Elasticsearch, Cassandra, and SPARQL.
The following option applies to Data Sources of all types.
unique.key.sets
Default
Required
No
Description
For data sources that do not express unique constraints in their metadata, either because unique constraints are not supported or because the data source did not include some or all of the valid constraints for reasons such as performance concerns, this property is used to define additional constraints manually. The property value is a comma-separated list of keys that define unique rows in a table. Each key is itself a comma-separated list of schema-qualified columns, enclosed in parentheses. For example, if table APP.CUSTOMERS has an ID column that serves as a primary key and a pair of columns, FNAME and LNAME, that together are a unique key, the value to express that is: (APP.CUSTOMERS.ID),(APP.CUSTOMERS.FNAME,APP.CUSTOMERS.LNAME)
JDBC Options
The following properties are used for all relational data sources.
jdbc.url
Default
Required
Yes
Description
The URL of the JDBC connection.
jdbc.username
Default
Required
No
Description
The username used to make the JDBC connection.
jdbc.password
Default
Required
No
Description
The password used to make the JDBC connection.
jdbc.driver
Default
Required
No
Description
The driver class name used to make the JDBC connection.
sql.dialect
Default
Inferred from supported JDBC drivers. ORACLE for unsupported drivers.
Required
No
Description
When using an unsupported JDBC driver, this option can be used to specify the format of the generated SQL. The options supported are ATHENA, BIGQUERY, DB2, DERBY, EXASOL, H2, HANA, HIVE, IMPALA, JIRA, MSSQL, MYSQL, ORACLE, POSTGRESQL, REDSHIFT, REST, SALESFORCE, SPARKSQL, SPLUNK, SYBASE, TERADATA
sql.schemas
Default
Required
No
Description
A comma-separated list of schemas to append to the schema search path. This option allows R2RML tables and queries to reference tables that are outside of the default schema for the connected user.
sql.default.schema
Default
Required
No
Description
Override the default schema for the connected user. Tables in the default schema may be referenced without qualification (mytable or "mytable" rather than myschema.mytable or "myschema"."mytable").
Tomcat Connection Pool Options
Additionally, connection pool properties for the built-in Tomcat connection pool are allowed. This set of additional allowed properties is listed in the Tomcat JDBC Connection Pool documentation. Stardog sets these connection pool defaults: