You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The username used to authenticate with the database.
null
password
char[]
The password used for authentication (can be encrypted).
null
url
char[]
The connection URL for the database (can be encrypted).
null or generated based on type and database.
timeout
int
The time in seconds before a connection attempt times out.
120 seconds
type
string
The type of database engine (e.g., oracle, postgresql, mariadb, mssql, informix, derby, h2, ...).
null
port
int
The port number to connect to the database.
null or generated based on type
database
string
The database name to connect to.
null
JDBC Source
<source-name>:
type: sqlquery: #
Attribute Key
Data Type
Description
type
string
Specifies the type of SQL source (sql).
query
string
The SQL query string to be executed (e.g., SELECT Column1, Column2 FROM TABLE).
To differentiate the current source, which executes inner SQL queries using the internal MetricsHub DB engine, we should consider renaming the type of the inner SQL source to reflect its engine-based nature. A suitable option could be coreSql.
Should we support for SELECT * FROM TABLE
If yes, we need to define a new attribute columns in the sql source.
Should we override the url in a source
If yes, we need to define a new attribute url, that overrides the user's url. It that, in the new url, macros should be correctly replaced by the engine.
The text was updated successfully, but these errors were encountered:
Specification
JDBC User's Configuration
metricshub.yaml
username
null
password
null
url
null
or generated based ontype
anddatabase
.timeout
120
secondstype
null
port
null
or generated based ontype
database
null
JDBC Source
type
sql
).query
SELECT Column1, Column2 FROM TABLE
).To differentiate the current source, which executes inner SQL queries using the internal MetricsHub DB engine, we should consider renaming the type of the inner SQL source to reflect its engine-based nature. A suitable option could be
coreSql
.SELECT * FROM TABLE
columns
in the sql source.url
, that overrides the user's url. It that, in the newurl
, macros should be correctly replaced by the engine.The text was updated successfully, but these errors were encountered: