Unify the way how we read configuration in Enceladus
オープン
Conformance
feature
priority: low
refactoring
Standardization
under discussion
- 主要言語
- Scala
- スター
- 33
- フォーク
- 16
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
## Background
The way how application configuration is read in `spark-job.jar` is a mess. Sometimes it's our own `ConfigReader` sometimes the typesafe config. There are same functions defined for it, sometimes as implicits sometimes as locla ones. Needs some unification
## Feature
Refactor the code to use only `ConfigReader` to access application configuration.
The only exception being Hypedrive plugin, where it's to be considered.
コントリビューションガイド
評価
この issue はまだ評価されていません。