AbsaOSS / AbsaOSS/enceladus

Better names for Standardization and Conformation jobs

Offen
#1,032 0 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
Conformance feature priority: undecided Standardization under discussion
Vorherrschende Sprache
Scala
Sterne
33
Forks
16
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.