Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-15317

Implement model to register datasets in SQuaSH

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: squash
    • Labels:
      None

      Description

      We need a model to register datasets in the SQuaSH DB. Currently, dataset attributes like dataset name and filter are stored and retrieved as/from job metadata, but it should be a separate table for that joinned with jobs or measurements table directly. This will likely expand in the future if we need to keep track of other attributes like ccd id, visit id or other data ids for a given dataset also.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-9293 squash support for multiple filters per dataset

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-15359 Query API resources by filter_name

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-14538 Remove ci_dataset from job model

          • To Do
          mentioned in

          Page Loading...

            Activity

            Hide
            Permalink
            afausti Angelo Fausti added a comment -

            We are dropping the SQuaSH MySQL DB in the Sasquatch re-implementation. Any change to the SQuaSH DB schema is not going to be implemented. The general idea is that this information is stored in the butler, and can be added as metadata to the lsst.verify job then sent to Kafka and persisted in InfluxDB or another format supported by Sasquatch.

            Show
            afausti Angelo Fausti added a comment - We are dropping the SQuaSH MySQL DB in the Sasquatch re-implementation. Any change to the SQuaSH DB schema is not going to be implemented. The general idea is that this information is stored in the butler, and can be added as metadata to the lsst.verify job then sent to Kafka and persisted in InfluxDB or another format supported by Sasquatch.

              People

              Assignee:
              afausti Angelo Fausti
              Reporter:
              afausti Angelo Fausti
              Watchers:
              Angelo Fausti, Simon Krughoff
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.