Refactor risk code to read exposure/vulnerability data from db

Bug #932743 reported by Muharem Hrnjadovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenQuake (deprecated)
Invalid
Medium
Muharem Hrnjadovic

Bug Description

Prerequisites: bug #932736, bug #932739 and bug #932742

Once the bugs above have been resolved we need to revise the risk logic so that it reads *all* exposure/vulnerability data from db directly.

Once we are at this point we can also stop writing exposure/vulnerability data to redis.

Changed in openquake:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Muharem Hrnjadovic (al-maisan)
milestone: none → 0.6.0
tags: added: 1model redis risk techdebt
tags: added: exposure vulnerability
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

Will tackle the exposure part first

Changed in openquake:
status: Confirmed → In Progress
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

The vulnerability data piece remains to be done.

Changed in openquake:
milestone: 0.6.0 → 0.6.1
Changed in openquake:
status: In Progress → Confirmed
Revision history for this message
Lars Butler (lars-butler) wrote :
Changed in openquake:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.