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

Migrate dp02 IDF registry to version 1 healpix dimensions

    XMLWordPrintable

    Details

      Description

      The dp02 registry on data-int.lsst.cloud needs to be migrated to use the healpix dimension universe. This should be an easy migration that is only involving a single change to the database and should take a few seconds.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          salnikov Andy Salnikov added a comment -

          Done, these are the commands that I needed to run for that:

          # register alembic revision branch for the new dimensions-config "manager" (v0)
          		 
          $ butler migrate stamp --namespace=daf_butler $REPO dimensions-config
          		 
           
          		 
          # upgrade to v1 (--namespace will no longer be needed after this migration)
          		 
          $ butler migrate upgrade --namespace=daf_butler $REPO 380002bcbb26

          Current status of all managers' versions:

          $ butler migrate show-current --namespace=daf_butler --butler $REPO
          		 
          attributes: lsst.daf.butler.registry.attributes.DefaultButlerAttributeManager 1.0.0 -> f22a777cf382
          		 
          collections: lsst.daf.butler.registry.collections.nameKey.NameKeyCollectionManager 2.0.0 -> 93341d68b814
          		 
          datasets: lsst.daf.butler.registry.datasets.byDimensions._manager.ByDimensionsDatasetRecordStorageManagerUUID 1.0.0 -> 2101fbf51ad3
          		 
          datastores: lsst.daf.butler.registry.bridge.monolithic.MonolithicDatastoreRegistryBridgeManager 0.2.0 -> a07b3b60e369
          		 
          dimensions: lsst.daf.butler.registry.dimensions.static.StaticDimensionRecordStorageManager 6.0.0 -> 87a30df8c8c5
          		 
          dimensions-config: daf_butler 1 -> 380002bcbb26
          		 
          opaque: lsst.daf.butler.registry.opaque.ByNameOpaqueTableStorageManager 0.2.0 -> 77e5b803ad3f

          Show
          salnikov Andy Salnikov added a comment - Done, these are the commands that I needed to run for that: # register alembic revision branch for the new dimensions-config "manager" (v0) $ butler migrate stamp --namespace=daf_butler $REPO dimensions-config   # upgrade to v1 (--namespace will no longer be needed after this migration) $ butler migrate upgrade --namespace=daf_butler $REPO 380002bcbb26 Current status of all managers' versions: $ butler migrate show-current --namespace=daf_butler --butler $REPO attributes: lsst.daf.butler.registry.attributes.DefaultButlerAttributeManager 1.0.0 -> f22a777cf382 collections: lsst.daf.butler.registry.collections.nameKey.NameKeyCollectionManager 2.0.0 -> 93341d68b814 datasets: lsst.daf.butler.registry.datasets.byDimensions._manager.ByDimensionsDatasetRecordStorageManagerUUID 1.0.0 -> 2101fbf51ad3 datastores: lsst.daf.butler.registry.bridge.monolithic.MonolithicDatastoreRegistryBridgeManager 0.2.0 -> a07b3b60e369 dimensions: lsst.daf.butler.registry.dimensions.static.StaticDimensionRecordStorageManager 6.0.0 -> 87a30df8c8c5 dimensions-config: daf_butler 1 -> 380002bcbb26 opaque: lsst.daf.butler.registry.opaque.ByNameOpaqueTableStorageManager 0.2.0 -> 77e5b803ad3f
          Hide
          Permalink
          salnikov Andy Salnikov added a comment -

          Nothing to review, closing the ticket., I ran few standard butler commands and it works fine.

          Show
          salnikov Andy Salnikov added a comment - Nothing to review, closing the ticket., I ran few standard butler commands and it works fine.

            People

            Assignee:
            salnikov Andy Salnikov
            Reporter:
            tjenness Tim Jenness
            Watchers:
            Andy Salnikov, Hsin-Fang Chiang, Jim Bosch, Tim Jenness
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.