Missing alternate view of an experiment crashing the start up of our web apps
Closed this issue · 1 comments
ke4 commented
Currently if an experiment has an alternative view
defined in its factor.xml
file and that other experiment is missing from the database, then our application stops when we try to start up the application and it is processing that experiment.
This is happening both in single cell
and bulk
as the logic is shared.
We have to replace this logic and implement the following if there is a missing alternative view
:
- Log it with an error status that the alternative view is missing from the database
- Send a notification to the developers/data prod team about the above fact
- The application loading should continue without processing the alternative view of that expariment
ke4 commented
Here lies the code that we have to refactor: https://github.com/ebi-gene-expression-group/atlas-web-core/blob/2dcf1d8e0e19f58be6971a3f642a50e2da3c1023/src/main/java/uk/ac/ebi/atlas/trader/factory/BaselineExperimentFactory.java#L80
extractAlternativeViews(String experimentAccession, BaselineExperimentConfiguration factorsConfig)