-
Notifications
You must be signed in to change notification settings - Fork 2
Configuration
The app.home
system property points to where the application is installed.
If not set, it uses the location of the configuration file as the home directory.
The work directory is a common location (usually within the home directory) where all the jobs can write their working data data.
The Work Directory itself can be used as a location to persist data between job runs. All jobs can use this directory to exchange data via files in this directory. It can be used as a batch exchange channel between jobs with jobs generating and modifying files in the working directory for other jobs to read. Note this is a very abstract data exchange mechanism as the jobs do not need to know anything about the jobs, only the data in the working directory.
Each transform engine will create their own working directory within the work directory using the name of the engine as the subdirectory name. If not specified in the job configuration, a random name will be generated to ensure data remains separate for each run. Jobs can persist data between runs in the job directory.
- Concepts
- Features
- Transform Engine
- Quick Start
- Configuration
- Secrets Vault
-
Readers
- List of Readers
- Custom Readers
-
Writers
- List of Writers
- Custom Writers
-
Filters
- Accept
- Reject
- Custom Filters
-
Tasks
- List of Tasks
- Custom Tasks
-
Validators
- List of Validators
- Custom Validators
-
Listeners
- List of Listeners
- Custom Listeners
-
Transforms
- List of Transforms
- Custom Transforms
- Mappers
- Context
- Databases
- Templates
- Logging
- Encryption
- Usage
- Expressions
- Examples