DPE Configuration
In on-premise deployments, the following properties configure Data Processing Engine (DPE) and are provided in the dpe/etc/application.properties file.
In addition, the following properties can be specified for DPE as well:
For self-managed and hybrid deployments, see also Network Connectivity and HTTP Proxy Configuration.
Basic settings
| Property | Data type | Description | ||
|---|---|---|---|---|
|
Boolean |
Enables debug logging mode.
If set to Default value: |
||
|
String |
Used to send information to Data Processing Manager (DPM) about the location of DPE. If DPM cannot reach DPE by the machine hostname, this property overrides that hostname. If not set, the hostname is determined by trying to resolve the DNS records for the Default value: |
||
|
Number |
Used to send information to DPM about the location of DPE. If DPM cannot reach DPE by the gRPC port, this property overrides that port. Default value: |
||
|
Number |
The HTTP server port for DPE. Default value: |
||
|
String |
A comma-separated list of environments in which this instance of DPE can be used. In the current release, this only affects user restrictions when accessing the file system data sources. |
||
|
String |
A meaningful name for DPE that is used in DPM Admin Console. This is especially useful in firewall-friendly mode as it makes it easier to identify DPE instances. We recommend using alphanumeric characters without spaces. If not set, the default value matches the hostname or the URL and the port of the DPE server.
In the firewall-friendly mode, the default value is |
||
|
Boolean |
When set to true , alerts are sent to Ataccama Support when an on-premise DPE disconnects from ONE. Default value:
|
DPE Labels
To configure the DPE label, use the property ataccama.one.dpe.label.
By default, the property is set to dpe, which means that all DPE instances where the label is not specifically set are grouped together.
You might want to group DPEs according to certain criteria, such as the connector settings for on-premise deployment.
To do this, set the ataccama.one.dpe.label property for each DPE to a value that is unique to that DPE instance.
For example, if you have two DPEs with different connector settings for on-premise deployment, you could set the ataccama.one.dpe.label property to dpe-onprem-1 for the first DPE and dpe-onprem-2 for the second DPE.
This would create two separate groups of DPEs, one for each connector setting.
|
DPEs with different configurations must not have the same label. If you need to make changes to a specific instance, be sure to give it a unique label. Only use shared labels when you expect the configuration to be identical in the same DPE replicas (for example, for cloud DPEs). |
Keycloak authentication
| Properties | Data type | Description |
|---|---|---|
|
String |
The URL of the server where Keycloak is running. Default value: |
|
String |
The name of the Keycloak realm. Default value: |
|
String |
The client identifier used to verify the admin user’s authorization token. Default value: |
|
String |
The secret key of the client identifier for the admin account. Secret keys can be generated using Keycloak. Default value: |
|
String |
The client identifier. Used to verify a user’s authorization token and to log in a user. Default value: |
|
String |
The secret key of the client. Secret keys can be generated using Keycloak. Default value: |
|
String |
Specifies the issuer of the JWT token. Typically, Keycloak uses the URL of the realm as the token issuer. Default value: |
|
String |
The type of client token authentication.
Possible values: Default value: |
|
String |
Points to the keystore file used for |
|
String |
The type of the keystore used for Default value: |
|
String |
The password of the keystore used for |
|
String |
The private key name specified in the keystore used for The default value is the client identifier. |
|
String |
The password for the private key. Used if the private key is encrypted. The default value is the keystore password. |
|
String |
Specifies for how long the JWT token used for authentication in Keycloak remains valid.
Used for Default value: |
gRPC Server
General settings
| Property | Data type | Description | ||
|---|---|---|---|---|
|
Number |
The port where the gRPC server is running. Default value: |
||
|
String |
Limits the size of messages that the gRPC server can process. The message size needs to fit in the working memory. Default value: |
||
|
Number |
The gRPC server request executor core pool size. Make sure this value is sufficient for the usual traffic in order to avoid creating additional connections because the current version of the gRPC library has the keep-alive for threads set to 0. Default value:
|
||
|
Number |
The gRPC server request executor max pool size. The queue length of executor is unlimited by default, and therefore the maximum pool size is effectively ignored. However, the value should be equal to or higher than the core pool size. Default value:
|
Authentication
| Property | Data type | Description |
|---|---|---|
|
Boolean |
Enables basic authentication on the gRPC Server. Default value: |
|
Boolean |
Enables bearer authentication on the gRPC Server. Default value: |
|
Boolean |
Enables internal JWT token authentication on the gRPC Server. Default value: |
|
Boolean |
Enables mTLS authentication on the gRPC Server. Default value: |
TLS/mTLS
| Property | Data type | Description |
|---|---|---|
|
Boolean |
Enables TLS authentication on the gRPC server.
When set to This property can be set for each DPE. Default value: |
|
String |
Defines whether mutual TLS authentication is enabled.
Possible values: When set to Disabled by default. |
|
Boolean |
Specifies whether the server allows all TLS connection attempts. Used if mTLS is enabled. |
|
String |
The full path to the TLS certificate, for example, |
|
String |
The full path to the private key of the certificate, for example, |
|
String |
The full path to the public certificate of the root certificate authority, for example, |
|
String |
The domain name of the generated server certificate. |
|
String |
The full path to the keystore containing private and public key certificates that are used by the gRPC server.
This property has a higher priority compared to |
|
String |
The type of keystore.
Possible values: |
|
String |
The password for the keystore. Used if the keystore is encrypted. |
|
String |
The private key name specified in the provided keystore. |
|
String |
The password for the private key of the gRPC server.
Required if If the key alias is not set, the password must be the same for all the items in the keystore. |
gRPC Client
General settings
| Property | Data type | Description |
|---|---|---|
|
String |
Limits the size of messages that the gRPC client can process. Default value: |
TLS/mTLS
| Property | Data type | Description |
|---|---|---|
|
Boolean |
Enables TLS authentication when communicating with the gRPC server. It also ensures that the communication with the server over gRPC is secure (encrypted instead of in plaintext) and guarantees the integrity of messages. Default value: |
|
Boolean |
Enables mutual TLS authentication between the server and the client. Default value: |
|
Boolean |
Specifies whether the gRPC client should verify the certificate of the server with which they communicate. Used if mTLS is enabled. |
|
String |
The full path to the TLS certificate, for example, |
|
String |
The full path to the private key of the certificate, for example, |
|
String |
The full path to the public certificate of the root certificate authority, for example, |
|
String |
The full path to a truststore file that contains public keys and certificates against which the client verifies the certificates from the server, for example, |
|
String |
The password for the truststore. Used if the truststore is encrypted. |
|
String |
The type of truststore.
Possible values: |
DPM connection
| Property | Data type | Description |
|---|---|---|
|
Number |
Defines how often DPE checks the connection to DPM. If there is no reply from DPM, DPE tries to register again with DPM. Expressed in milliseconds. Default value: |
|
String |
The name of the gRPC channel that DPE uses to communicate with DPM. Default value: |
|
String |
The IP address or the URL of the server where DPM is running. Default value: |
|
Number |
The port where the gRPC server is running. Default value: |
|
Boolean |
Enables TLS for the connection to DPM. Default value: |
|
String |
Defines whether mutual TLS authentication is enabled.
Possible values: When set to Disabled by default. |
|
Boolean |
Specifies whether the gRPC client should verify the certificate of the server with which they communicate. Used if mTLS is enabled. |
|
String |
The full path to the TLS certificate, for example, |
|
String |
The full path to the private key of the certificate, for example, |
|
String |
The full path to the public certificate of the root certificate authority, for example, |
|
String |
The full path to a truststore file that contains public keys and certificates against which the client verifies the certificates from the server, for example, |
|
String |
The password for the truststore. Used if the truststore is encrypted. |
|
String |
The type of truststore.
Possible values: |
Communication mode between DPE and DPM
Use these settings to turn on communication over bidirectional gRPC stream between DPE and DPM. When this firewall-friendly mode is configured, the follow-up communication from DPM to DPE, such as browsing queries or submitting jobs, does not require opening DPE’s inbound ports to the outside world.
In cases when firewall-friendly mode cannot be configured, the TLS security can be set for all DPE by setting the DPM property ataccama.one.dpm.registry.enforce-tls or by enabling TLS security on selected DPE instances.
We recommend checking the desired security level if any of your DPE instances communicate with DPM via internet.
| Property | Data type | Description | ||
|---|---|---|---|---|
|
String |
Defines how DPE connects to DPM. The following options are available:
Default value: |
||
|
String |
Defines how long DPE waits for the in-process server shutdown before shutting it down forcefully.
Used only if Default value: |
||
|
String |
Sets the maximum period of time that DPE waits for a new request from DPM before it attempts to register again.
Used only if Default value: |
MDM connection
| Property | Data type | Description |
|---|---|---|
|
Boolean |
If set to Default value: |
|
Boolean |
Enables TLS authentication when communicating with MDM. |
|
String |
The full path to the truststore, for example, |
|
String |
The password for the truststore. |
Plugins and JDBC drivers
| Property | Data type | Description |
|---|---|---|
|
String |
The location of the plugins folder. Default value: |
|
String |
Points to the folder containing the JDBC drivers used by DPE. Default value: |
|
String |
The connection entity name used in the metadata model (MMD) for local file systems. |
|
String |
The connection entity name used in the metadata model (MMD) for ONE MDM data source. |
|
String |
The connection entity name used in the metadata model (MMD) for ONE RDM data source. |
|
String |
The connection entity name used in the metadata model (MMD) for S3 data source. |
Query pushdown processing
The default pushdown configuration creates one SQL query for each table column and retrieves all supported statistics at once.
It is possible to modify the number of DPE threads and the number of columns processed by a single query and to split standard and frequency analysis.
In the property keys, replace <data_source_type> with the identifier for your source: bigquery, databricks, iomete, or synapse.
See also Pushdown profiling retry configuration.
For DQ evaluation settings, see DQ pushdown processing. For source-specific settings, see Databricks query pushdown processing and Snowflake query pushdown processing.
| Property | Data type | Description |
|---|---|---|
|
Number |
The number of columns processed at once when fetching basic statistics.
This property is irrelevant if Default value: |
|
Number |
The number of columns processed at once when fetching frequencies or merged statistics. Default value: Snowflake uses different defaults for tables and views. See Snowflake query pushdown processing. |
|
Boolean |
Get both basic statistics and frequencies at once (for a group of columns). Default value: |
|
Number |
The number of queries processed at once. This setting limits the number of queries sent from DPE to the data source for profiling. It is applied globally for the whole DPE and the number of allowed queries is shared between all pushdown profiling jobs for that data source. If the connection pool is exhausted, DPE waits for a connection to become available instead of failing the query. Default value: |
|
Number |
The maximum length of string values stored as samples in profiling results (for example, in frequency analysis or quantiles and other value distributions). This doesn’t affect calculations such as length statistics, masks, or patterns, which use the full string to compute. When a string exceeds this limit, it is truncated as follows: the beginning of the string is preserved in the length specific, the number of omitted characters is reported, and the rest of the string is displayed as a hash value. The hash ensures uniqueness of truncated values. Default value: For non-pushdown profiling, see |
DQ pushdown processing
The following properties configure how DPE evaluates data quality in pushdown. Once set, they apply to all connections of the given data source type processed by the DPE. To learn how DQ evaluation in pushdown works, see How pushdown for DQ evaluation works.
In the property keys, replace <data_source_type> with the identifier for your source: snowflake, databricks, bigquery, or iomete.
The properties don’t apply to Azure Synapse, which evaluates DQ in a single pass without intermediate tables.
| Property | Data type | Description |
|---|---|---|
|
Boolean |
Takes a snapshot of the source before a DQ job runs, so that the rule evaluation and the follow-up read that fetches invalid record samples or exported records use the same data. Set to On Databricks, BigQuery, and IOMETE, the snapshot is stored as a table in the operational database. On Snowflake, it’s a temporary table, so nothing is left in your schema. Default value: |
|
Boolean |
Logs the SQL statements generated for DQ jobs and the rows fetched. Use only for troubleshooting: the output is verbose and doesn’t add detail about failures. Changing this property requires restarting DPE. Default value: |
Databricks query pushdown processing
The following properties are specific to Databricks pushdown processing. For properties shared with other data sources, see Query pushdown processing, DQ pushdown processing, and Pushdown profiling retry configuration.
When profiling large tables, Databricks pushdown can estimate standard deviation and variance from a sample of rows instead of reading every row. All other statistics, such as count, minimum, maximum, average, sum, and quantiles, are always computed over every row. Unmaterialized views and SQL catalog items are never sampled, because determining their size would require running the query.
The sampling error is negligible, for example, at 2.2 billion sampled rows, the relative standard error of the variance is about 0.003%.
| Property | Data type | Description |
|---|---|---|
|
Number |
The number of rows above which standard deviation and variance are estimated from a sample. For tables with this many rows or fewer, both statistics are computed exactly. Set a negative value to always compute them exactly, or Default value: |
|
Number |
The percentage of rows sampled when a table exceeds the Default value: |
Snowflake query pushdown processing
The following properties are specific to Snowflake pushdown processing. For properties shared with other data sources, see Query pushdown processing, DQ pushdown processing, and Pushdown profiling retry configuration.
| Property | Data type | Description |
|---|---|---|
|
String |
Sets the period of time after which Snowflake queries that are still running are canceled. Default value: |
|
String |
Specifies how queries are created.
Possible values: The Default value: |
|
Number |
Defines how many values are computed in a single query. Currently applies only to the basic count query. To turn the feature off, pick a large number, such as Default value: |
|
String |
Defines which mask function is used.
Possible values: The Default value: |
|
Number |
The number of columns profiled in a single query when the source is a table or a materialized copy of a view. Default value: |
|
Number |
The number of columns profiled in a single query when the source is a view or an SQL catalog item that isn’t materialized.
If not set, the value of Default value: |
|
Number |
The maximum length of string values stored as samples in profiling results (for example, in frequency analysis or quantiles and other value distributions). This doesn’t affect calculations such as length statistics, masks, or patterns, which use the full string to compute. When a string exceeds this limit, it is truncated as follows: the beginning of the string is preserved in the length specified, the number of omitted characters is reported, and the rest of the string is displayed as a hash value. The hash ensures uniqueness of truncated values. Default value: For non-pushdown profiling, see |
|
Boolean |
Applies to Legacy pushdown only. Evaluates the source once so that every pass of a DQ job reads identical rows. No tables are created in Snowflake. Turn on only if the source can change between reads, for example, a view over Default value: |
|
Boolean |
Enables automatic upload of user-defined functions to Snowflake. Default value: |
|
String |
Specifies how long to keep unused user-defined function definitions before they are removed. Default value: |
|
String |
Specifies the age at which lookups with ready status are considered for removal, if a newer version of the lookup exists. Default value: |
|
Number |
Specifies how many keys are uploaded in a batch during lookup upload. Default value: |
|
Number |
Specifies the maximum number of keys when uploading lookup tables. Larger lookup tables are inserted into a temporary table. Default value: |
|
String |
Specifies how often to check and clean old lookups. Default value: |
|
String |
Specifies how often to poll for lookups being initialized in another session. Default value: |
|
String |
Specifies the amount of time before a lookup with initializing status is considered for removal. Default value: |
|
String |
Specifies the age at which lookups with ready status are considered for removal, if no newer version of the lookup exists. Default value: |
|
Integer |
Specifies the maximum total number of filter combinations in monitoring project attribute filters. If this limit is exceeded, the monitoring job fails. Increasing this limit might result in higher resource consumption on the database side. Default value: |
|
String |
If set to Default value: |
|
Number |
The number of times DPE retries to submit a query to Snowflake in case of a recoverable error (such as Default value: Applies to legacy pushdown processing; for the non-legacy implementation, see Pushdown profiling retry configuration. |
|
String |
The maximum delay between Snowflake query submit retries in case of a recoverable error. Default value: Applies to legacy pushdown processing; for the non-legacy implementation, see Pushdown profiling retry configuration. |
Lookup cache configuration for BigQuery, Databricks, IOMETE, and Synapse
The BigQueryPlugin, DatabricksPlugin, IOMETEPlugin, and SynapsePlugin pushdown data sources share the same lookup upload and cleanup configuration.
In the property keys, replace <data_source_type> with the identifier for your source: bigquery, databricks, iomete, or synapse.
These properties are similar to the Snowflake-specific lookup properties described in Snowflake query pushdown processing, but are not identical:
-
lookup-larger-size-bytes-boundarycounts the lookup table size in bytes, whereas the Snowflake equivalent,lookup-larger-size-boundary, counts the number of keys. -
lookup-upload-max-retrieshas no Snowflake equivalent; Snowflake instead hasudf-sync-enabledandudf-max-agefor its user-defined function synchronization, which the other data sources don’t use. -
The default value of
lookup-upload-batch-sizeis1000forbigqueryandsynapse, but50000fordatabricksandiomete.
| Property | Data type | Description |
|---|---|---|
|
Number |
Specifies how many keys are uploaded in a batch during lookup upload. Default value: |
|
Number |
Specifies the maximum lookup table size, in bytes, that is inlined into the query. Larger lookup tables are uploaded to a temporary table instead. Default value: |
|
Number |
The number of times DPE retries uploading a lookup table if the upload fails. Default value: |
|
String |
Specifies how often to check and clean old lookups. Default value: |
|
String |
Specifies how often to poll for lookups being initialized in another session. Default value: |
|
String |
Specifies the amount of time before a lookup with initializing status is considered for removal. Default value: |
|
String |
Specifies the age at which lookups with ready status are considered for removal, if a newer version of the lookup exists. Default value: |
|
String |
Specifies the age at which lookups with ready status are considered for removal, if no newer version of the lookup exists. Default value: |
Pushdown profiling retry configuration
The following properties control how pushdown profiling handles transient query failures.
In the property keys, replace <data_source_type> with the identifier for your source: bigquery, databricks, iomete, snowflake or synapse.
For Snowflake, this applies only to non-legacy pushdown processing, althought the same property names are also used for legacy pushdown processing. If retry settings are not explicitly configured, each implementation uses its own default value. If configured, the values apply to both implementations, with differences in respective behaviors.
Retries apply only to transient failures: errors such as insufficient permissions, invalid credentials, or query syntax errors are not retried and fail immediately.
If any query exhausts all retry attempts or encounters a non-retryable error, the whole profiling job is canceled. If the connection pool is exhausted, DPE waits for a connection to become available instead of failing the query.
| Property | Data type | Description |
|---|---|---|
|
Number |
The total number of attempts to submit a pushdown profiling query in case of a recoverable error, including the initial attempt. To turn off retries, set the property to Default value: |
|
String |
The delay before the first retry attempt.
The delay doubles with each subsequent retry, up to the limit set in Possible values: Default value: |
|
String |
The maximum delay between retry attempts. Possible values: Default value: |
Profiling
These settings configure how profiling results are stored and displayed.
| Property | Data type | Description |
|---|---|---|
|
Number |
The maximum length of string values stored as samples in profiling results (for example, in frequency analysis or quantiles and other value distributions). This doesn’t affect calculations such as length statistics, masks, or patterns, which use the full string to compute. When a string exceeds this limit, it is truncated as follows: the beginning of the string is preserved in the length specified, the number of omitted characters is reported, and the rest of the string is displayed as a hash value. The hash ensures uniqueness of truncated values. Default value: |
DataConnect plugin
The DataConnect plugin is used to query metadata in a particular data source. The retrieved information can be cached.
| Property | Data type | Description |
|---|---|---|
|
Number |
The maximum number of threads that can be dedicated to closing the clients that have been evicted. Default value: |
|
Boolean |
If set to Default value: |
|
Number |
The maximum size of the DataConnect cache for all data sources. The value refers to the number of cached client instances, where each instance corresponds to a combined definition of a data source and one of its credentials. To disable caching, set the value to Default value: |
|
Number |
The maximum number of browse query results that are cached for each DataSource client. Default value: |
|
String |
Specifies for how long the entries are stored in the cache. Default value: |
|
String |
Defines for how long the DataSource client cache stores items for browsing. Starting from 14.1.0, the cache is cleared after this period expires. Default value: |
File system
| Property | Data type | Description | ||
|---|---|---|---|---|
|
String |
The root path of the default mounted file system. It is possible to set up multiple file systems in the same DPE. These folders can be used for profiling and browsing data in MMM. To add another file system, replace the name of the file system (
|
||
|
String |
Restricts which roles are allowed to work with a particular file system.
To set limitations for another file system, make sure to provide the correct file system name and the environment name, for example, |
||
|
String |
The sample file size for items loaded from local file systems.
Used to detect the content type, such as Default value: |
||
|
Number |
The number of sheet rows, including the header row, that are sampled to detect the data types of columns when metadata is imported for Microsoft Excel (XLS and XLSX) files. Applies to Excel files from all file-based sources, not only local file systems. To sample all rows of the sheet, set the property to Regardless of the row limit size, the full file is read at each import. A larger sample makes incorrect type detection less likely but takes longer on large sheets and uses more processing capacity. Default value: |
ONE Object Storage
| Property | Data type | Description |
|---|---|---|
|
Boolean |
If set to Default value: |
|
Number |
Defines how often the object storage is checked for objects that need to be removed following a storage failure. Expressed in milliseconds. Default value: |
Persistent storage
Persistent storage is intended to work as DPE’s internal storage. This means that it should not store any user data or, in general, use a database with user data.
There are two types of persistent storage: the default embedded database and a custom data source.
Using a custom data source instead of the embedded one is optional and requires further configuration.
The driver required for the custom data source must be manually added to the lib folder with other database drivers.
| Property | Data type | Description |
|---|---|---|
|
String |
The type of data source for persistent storage.
If you are using the default embedded database, set the value to Default value: |
|
String |
Points to the folder storing the persisted data. Persisted data includes all application data, files for processing, and processing results. Default value: |
Custom data source
| Property | Data type | Description |
|---|---|---|
|
String |
The JDBC driver class name for the custom data source for persistent storage, for example, |
|
String |
A JDBC connection string pointing to the custom data source for persistent storage, for example, |
|
String |
The username for the custom data source for persistent storage. Default value: |
|
String |
The password for the custom data source persistent storage. Default value: |
Executor
|
When setting any launch parameters, make sure the property values (such as file paths) do not include any space characters. This also applies to values in Compare the following examples:
|
| Property | Data type | Description | ||
|---|---|---|---|---|
|
String |
The classpath delimiter used for libraries for local jobs. Default value: |
||
|
String |
The libraries needed for local jobs.
Jobs are stored as Starting from 13.4.0, all JDBC libraries need to be specified here in order to use the You can specify:
Default value: |
||
|
String |
The directory that holds temporary work files for local jobs.
A folder is created for each job within this directory, with the name containing the If not specified, the system environment variable After each job finishes, the corresponding work files are automatically deleted from this directory.
|
||
|
String |
References the script for customizing how local jobs are launched.
For example, you can change which shell script is used to start the job.
The script is located in the The default value for Linux is
|
||
|
String |
(Optional) Excludes certain Java libraries and drivers that are in the same classpath but are not needed for processing. Each library needs to be prefixed by an exclamation mark ( Example: |
||
|
String |
Points to the location of Ataccama licenses needed for local jobs.
Configure it only if licenses are stored outside of the standard locations, that is, the user home directory and the folder Starting from 17.2.0, engines that connect to Ataccama Cloud, including hybrid DPEs on your own infrastructure, don’t need a license file as DPM provides a signed token with each job instead. The property is relevant only for self-managed deployments, where DPM also runs on your side. Default value: |
||
|
String |
Sets the The runtime is compatible with Java 8 or later. |
||
|
String |
Configures any environment variable for running local jobs. To set a custom environment variable, provide the name of the variable instead of the placeholder |
||
plugin.executor-launch-model.ataccama.one.launch-type-properties.LOCAL.job-specific-system-properties.allowed-keys plugin.executor-launch-model.ataccama.one.launch-type-properties.SPARK.job-specific-system-properties.allowed-keys |
String |
A comma-separated list of keys identifying the system properties that can be set when submitting a job, which makes their values specific for a particular job.
These job-specific system properties are then passed to each spawned runtime JVM associated with the identified launch type ( |
||
|
Boolean |
If set to Default value: |
||
|
String |
Specifies the time period after which job results are deleted from DPE, starting from when the job finishes. Typically, the property serves as a backup in case job files could not be deleted after the job was completed. This option applies regardless of how the property Default value: |
||
|
Number |
Defines how often DPM checks for recently completed jobs in DPE. Expressed in milliseconds. Default value: |
||
|
Number |
The number of old jobs to be cleaned at once. Default value: |
||
|
Number |
The maximum duration of each job-cleaning run.
This property must be set with respect to Default value: |
||
|
Number |
The maximum number of processes or threads that can be run in parallel on this engine. Starting from 17.2.0, DPM also enforces a limit across all engines. See Concurrent job limit and license. Default value (self-managed and hybrid deployments): Default value (Ataccama Cloud deployments):
|
||
|
Boolean |
Enables notifications over gRPC from the ONE runtime server for runtime jobs. Default value: |
||
|
Boolean |
Enables notifications over gRPC from the ONE runtime server for data quality monitoring jobs. Default value: |
||
|
String |
A regular expression matching the names of environment variables set for DPE that can be accessed by child processes spawned for runtime jobs. Default value: |
||
|
Number |
The required number of evaluation threads. To set this, use
The variable defines the number of models which are processed in parallel in the DQ engine. Default value: |
||
|
Boolean |
Set this property to To set this, use
For more information about the query limits, see Data Sources Configuration, section Troubleshooting. Default value: |
||
|
Number |
Batch limit for component rules.
To set this using
Default value: |
Shutdown
| Property | Data type | Description |
|---|---|---|
|
String |
The type of application shutdown. If set to Default value: |
|
String |
Defines how long a shutdown phase can last. After this time expires, the application shuts down regardless of any active requests. Default value: |
|
Boolean |
If set to The waiting period is defined through the property |
|
String |
How long the application waits for running jobs to complete before shutting down gracefully. Once the timeout is reached, any remaining jobs are canceled. Should be shorter than the value set in Default value: |
Was this page useful?