Status: To Do
Fix Version/s: None
The ci_dataset field was added to the job table for performance reasons when filtering the jobs by dataset. It is also present in the env JSON field.
Consider the removal of this field from the job table:
1) compare the performance when querying the ci_dataset field in the Job table and querying ci_dataset in the env JSON field.
2) have in mind that when supporting multiple environments the name of this field may change
Hi Krzysztof Findeisen this ticket addresses an issue in the SQuaSH MySQL database model where ci_dataset is present in two different places.
You can see for example how a verification job from ap_verify is stored in SQuaSH
This issue is known for some time and I would like to fix it as part of the work in DM-18057.
But the answer is yes, ci_dataset will still be mapped to an InfluxDB tag along with other metadata and it will be available through the Chronograf UI for filtering etc.
Will we still be able to query a dataset ID from Chronograf after the ci_dataset tag is removed? It's not clear from the description, and I can't find an env in the online database.