Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:7
-
Epic Link:
-
Team:SQuaRE
Attachments
Issue Links
- blocks
-
DM-12603 Deployment of the squash-restful-api service
- Done
-
DM-12600 Implement pagination and caching in the Flask REST API
- Invalid
- is blocked by
-
DM-12191 Definition of the Flask extensions to be used in the SQuaSH REST API
- Done
-
DM-12193 Redesign SQuaSH QC Tier 0 database to allow measurements from different lsst.verify packages
- Done
- relates to
-
DM-13122 Separate the execution environment metadata from the other metadata in the JSON document sent to SQuaSH (dispatch_verify.py)
- Done
-
DM-9876 [some] validate_drp derived metric values visualization is mangled in dashboard
- Done
-
DM-12231 Investigate GraphQL as an alternative to Django REST Framework for the squash-api microservice
- Done
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Summary | Redesign squash-api | Redesign SQuaSH REST API |
Story Points | 7 |
Story Points | 7 | 4.2 |
Summary | Redesign SQuaSH REST API | Redesign SQuaSH REST API to make it complaint with lsst.verify |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Story Points | 4.2 | 2.8 |
Attachment | qc-0-db.png [ 30805 ] |
Story Points | 2.8 | 7 |
Resolution | Done [ 10000 ] | |
Status | In Progress [ 3 ] | Done [ 10002 ] |
The SQuaSH database models follow closely the objects defined in the lsst.verify package. The
database entities are:
metric, spec
and their relationships are:
The current model is meant to support multiple execution environments,
such as jenkins or the local user environment. The metadata associated
to these environments is stored in the job table and can be used to look
up for the corresponding job object.
This implementation uses JSON() datatype in MySQL
See the https://sqr-009.lsst.io technote for details.