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

FY20 Define Procedures and Build Tools for Schema Evolution

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Database
    • Labels:
      None
    • Epic Name:
      FY20 Schema Evolution
    • Story Points:
      79
    • WBS:
      02C.06.01.01
    • Team:
      Data Access and Database

      Description

      As described in LDM-135, The database system must allow for occasional schema changes for the Level 1 data, and occasional changes that do not alter query results for the Level 2 data after the data has been released. This epic involves preparing for dealing with schema changes in production syste.

        Attachments

          Issue Links

          mentioned in

          Page Loading...

            Activity

            Hide
            Permalink
            fritzm Fritz Mueller added a comment -

            Note that this is schema evolution for loaded catalog data, not schema migration for qserv metatdata (qmeta) as currently addressed by "smig" tool. This would involve some support for allocating and using reserved "extra" columns in the catalog schema.

            Show
            fritzm Fritz Mueller added a comment - Note that this is schema evolution for loaded catalog data, not schema migration for qserv metatdata (qmeta) as currently addressed by "smig" tool. This would involve some support for allocating and using reserved "extra" columns in the catalog schema.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fritzm Fritz Mueller
              Watchers:
              Fritz Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.