AbsaOSS / AbsaOSS/enceladus

Better names for Standardization and Conformation jobs

Open
#1,032 0 comments 1 reaction 0 assignees View on GitHub
Conformance feature priority: undecided Standardization under discussion
Dominant language
Scala
Stars
33
Forks
16
PR merge metrics
No merged PRs in 30d

Description

## 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.