Provides Database Connection Pooling Service based on HikariCP. Connections can be asked from pool and returned after usage.
dbcp, hikari, jdbc, database, connection, pooling, store
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Database Connection URL | hikaricp-connection-url | A database connection URL used to connect to a database. May contain database system name, host, port, database name and some parameters. The exact syntax of a database connection URL is specified by your DBMS. Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Database Driver Class Name | hikaricp-driver-classname | The fully-qualified class name of the JDBC driver. Example: com.mysql.jdbc.Driver Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Database Driver Location(s) | hikaricp-driver-locations | Comma-separated list of files/folders and/or URLs containing the driver JAR and its dependencies (if any). For example '/var/tmp/mariadb-java-client-1.1.7.jar' This property expects a comma-separated list of resources. Each of the resources may be of any of the following types: directory, URL, file. Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Kerberos User Service | hikaricp-kerberos-user-service | Controller Service API: KerberosUserService Implementations: KerberosKeytabUserService KerberosPasswordUserService KerberosTicketCacheUserService | Specifies the Kerberos User Controller Service that should be used for authenticating with Kerberos | |
| Database User | hikaricp-username | Database user name Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Password | hikaricp-password | The password for the database user Sensitive Property: true Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Max Wait Time | hikaricp-max-wait-time | 500 millis | The maximum amount of time that the pool will wait (when there are no available connections) for a connection to be returned before failing, or 0 <time units> to wait indefinitely. Supports Expression Language: true (will be evaluated using variable registry only) | |
| Max Total Connections | hikaricp-max-total-conns | 10 | This property controls the maximum size that the pool is allowed to reach, including both idle and in-use connections. Basically this value will determine the maximum number of actual connections to the database backend. A reasonable value for this is best determined by your execution environment. When the pool reaches this size, and no idle connections are available, the service will block for up to connectionTimeout milliseconds before timing out. Supports Expression Language: true (will be evaluated using variable registry only) | |
| Validation Query | hikaricp-validation-query | Validation Query used to validate connections before returning them. When connection is invalid, it gets dropped and new valid connection will be returned. NOTE: Using validation might have some performance penalty. Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Minimum Idle Connections | hikaricp-min-idle-conns | 10 | This property controls the minimum number of idle connections that HikariCP tries to maintain in the pool. If the idle connections dip below this value and total connections in the pool are less than 'Max Total Connections', HikariCP will make a best effort to add additional connections quickly and efficiently. It is recommended that this property to be set equal to 'Max Total Connections'. Supports Expression Language: true (will be evaluated using variable registry only) | |
| Max Connection Lifetime | hikaricp-max-conn-lifetime | -1 | The maximum lifetime in milliseconds of a connection. After this time is exceeded the connection will fail the next activation, passivation or validation test. A value of zero or less means the connection has an infinite lifetime. Supports Expression Language: true (will be evaluated using variable registry only) |
Supports Sensitive Dynamic Properties: Yes
Dynamic Properties allow the user to specify both the name and value of a property.
| Name | Value | Description |
|---|---|---|
| JDBC property name | JDBC property value | Specifies a property name and value to be set on the JDBC connection(s). If Expression Language is used, evaluation will be performed upon the controller service being enabled. Note that no flow file input (attributes, e.g.) is available for use in Expression Language constructs for these properties. Supports Expression Language: true (will be evaluated using variable registry only) |
| Required Permission | Explanation |
|---|---|
| reference remote resources | Database Driver Location can reference resources over HTTP |