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

Add registry support for ephemeral dataset locations

    XMLWordPrintable

    Details

    • Story Points:
      2
    • Team:
      Data Release Production

      Description

      Add Registry APIs that would allow an InMemoryDatastore to add entries to the (logical) dataset location table in a way that would automatically expire when the connection to the database is closed.

      This would probably be best done via temporary tables, and I think that ought to be doable even in Oracle where - as I understand it - only the rows (not the table existence and definition) are temporary.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            Since this is for in-memory datastore it's probably fair to say that this ticket isn't a gen2 deprecation blocker (since in-memory datastore is not a required gen2 feature). I will remove that label. It's probably debatable whether it's a registry incompatibility blocker either since it seems like we can make these changes without touching other datastores and since in-memory is by definition created from scratch each time no-one should notice.

            Immediately writing in-memory datasets to dataset_location_trash might be an acceptable middle ground so long as in-memory datastore kept track of things internally – it depends really on how registry is going to look at the dataset_location table (currently no-one looks at it outside of datastore).

            Show
            tjenness Tim Jenness added a comment - Since this is for in-memory datastore it's probably fair to say that this ticket isn't a gen2 deprecation blocker (since in-memory datastore is not a required gen2 feature). I will remove that label. It's probably debatable whether it's a registry incompatibility blocker either since it seems like we can make these changes without touching other datastores and since in-memory is by definition created from scratch each time no-one should notice. Immediately writing in-memory datasets to dataset_location_trash might be an acceptable middle ground so long as in-memory datastore kept track of things internally – it depends really on how registry is going to look at the dataset_location table (currently no-one looks at it outside of datastore).

              People

              Assignee:
              jbosch Jim Bosch
              Reporter:
              jbosch Jim Bosch
              Watchers:
              Jim Bosch, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.