Environment Configuration - ja-guzzle/guzzle_docs GitHub Wiki

To provide the abstraction for the different frameworks like ingestion, data load etc when accessing . Also to keep the configuration portable across environment and even support for running the jobs in the context of SIT or UAT env from the same deployment shall be possible.

The logical endpoint of a particular data source / target will. This will typically capture the : Name, Data store type (or technology), custom properties (like commit supported),

Represent the physical data endpoint can capture physical connection details. Will capture the JDBC URL (or host name, port), provide pre- and post-connection hooks, failover (for sources like Hive and Hbase - we should use ZK urls)

Provides the mappings of set of logical end points to physical end point. An env file typical represent one physical env with combination of source and target database to be used

The jobs will refer to Logical data endpoints. While when invoking the jobs the Environment config will be provided to resolve the logical data endpoints to physical end points.