The MariaDB/MySQL datasource plugin enables Quasar to load data from MariaDB, MySQL or other protocol-compliant stores. Most native column types are supported with the notable exception of BINARY
/BLOB
variants and all GEOMETRY
types.
JSON configuration required to construct a MariaDB datasource.
{
"connection": <connection-configuration>
}
connection
: A connection configuration object.
The MariaDB/MySQL destination plugin enables Quasar to load data into MariaDB, MySQL or other protocol-compliant stores. Loading is done via the LOAD DATA LOCAL INFILE
statement to achieve good performance.
Please ensure the destination server has LOCAL INFILE
support enabled.
JSON configuration required to construct a MariaDB destination.
{
"connection": <connection-configuration>,
"writeMode": "create" | "replace" | "truncate" | "append"
}
connection
: A connection configuration object.writeMode
: Indicates how to handle loading data into an existing tablecreate
: prevent loading data into an existing table, erroring if it existsreplace
:DROP
and recreate an existing table prior to loading datatruncate
:TRUNCATE
an existing table prior to loading dataappend
: appends to an existing table, creating it if it doesn't exist
JSON configurating describing how to connect to MariaDB.
{
"jdbcUrl": String
[, "maxConcurrency": Number]
[, "maxLifetimeSecs": Number]
}
jdbcUrl
: a MariaDB connection string. Note that any connection parameter values containing URI reserved characters must be percent encoded to avoid ambiguity.maxConcurrency
(optional): the maximum number of simultaneous connections to the database (default: 8)maxLifetimeSecs
(optional): the maximum lifetime, in seconds, of idle connections. If your database or infrastructure imposes any limit on idle connections, make sure to set this value to at most a few seconds less than the limit (default: 300 seconds)