AbsaOSS / AbsaOSS/enceladus

Better names for Standardization and Conformation jobs

未关闭
#1,032 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
Conformance feature priority: undecided Standardization under discussion
主要语言
Scala
星标
33
派生
16
PR 合并指标
30 天内没有已合并 PR

描述

## Background
The discussion about better naming of jobs was started in PR #1009.
Here are the suggestions.

@Zejnilovic siggested
> This might prove hard to read. This would then say
> ```
> Dynamic Conformance 1.5.0 ComplexDataStructures 21 2019-01-01 1
> ```
> how about something like
> ```
> Dynamic Conformance 1.5.0 - ComplexDataStructures(v. 21) 2019-01-01, v. 1
> ```
> Or something similar.

@DzMakatun
> 1. As one of the potential uses is to filter json from Spark History API, I would suggest to keep the parsing as simple as possible. So lets keep it with the spaces only.
> 2. I would also remove the word "Dynamic", to keep it consistent with Standardization naming, and, also a bit shorter.

## Feature
The idea is to change Standardization and Conformance job names to something that is
* Easier to understand by users
* Be parsable so that Spark history can be analyzed easier.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。