ScalarDB SQL Configurations
This document explains the configurations of ScalarDB SQL.
ScalarDB SQL offers two connection modes: Direct and Server modes. With Direct mode, ScalarDB SQL client-side library directly uses ScalarDB API. On the other hand, with Server mode, ScalarDB SQL client-side library uses ScalarDB API indirectly through ScalarDB SQL Server.
There are Direct mode specific configurations and Server mode specific configurations. So we first explain the common configurations, then the Direct mode specific configurations, and the Server mode specific configurations. And lastly, we explain the ScalarDB SQL Server configurations.
Common configurations
The common configurations are as follows:
name | description | default |
---|---|---|
scalar.db.sql.default_transaction_mode | Default transaction mode. TRANSACTION or TWO_PHASE_COMMIT_TRANSACTION can be set. | TRANSACTION |
scalar.db.sql.connection_mode | Connection mode. DIRECT or SERVER can be set. | DIRECT |
Configurations for Direct mode
The configurations for Direct mode are as follows:
name | description | default |
---|---|---|
scalar.db.sql.statement_cache.enabled | Enable the statement cache. | false |
scalar.db.sql.statement_cache.size | The maximum number of cached statement. | 100 |
Note that in the Direct mode, you need to configure underlining storage/database, as well. Please see Getting Started with ScalarDB for the details of the underlining storage/database configurations.
Please see also ScalarDB SQL Server for the details of ScalarDB SQL Server.