Closed rosibaj closed 3 years ago
Maestro already has updated_at
for file_centric and analysis_centric:
https://github.com/overture-stack/maestro/blob/7f3388a10bc9e280952cc27fb450c7314b76118c/maestro-app/src/main/resources/analysis_centric.json#L79
https://github.com/overture-stack/maestro/blob/029187d6f54b082d74e0e28516aaaa767e23c233/maestro-app/src/main/resources/file_centric.json#L106
And I have verified these are the mappings in use in dev and qa.
env | file_centric | analysis_centric |
---|---|---|
DEV | ||
QA |
I can't see the mapping in use in prod but it must contain updated_at (at least for analysis_centric) because we are able to sort by updadedAt on analysis with no error:
Also song-search is already set to convert values from es from snake-case: https://github.com/icgc-argo/song-search/blob/24842f7c12accae88777bf093b332b346ccaae7e/src/main/java/bio/overture/songsearch/model/Analysis.java#L34
follow up on this
I've confirmed that the mappings for file-centric and analysis-centric in prod have the updated_at date field in their mappings.
Describe the bug
Error log reported by @henro001:
From the indicies:
Expected behaviour
file centric
andanalysis centric
mappings to repo to reflect the new fields