Enable Support for Changing Field Types

[jordanpadams]

💡 Description

We need to be able to support the possibility a field is created in the registry at some point in time, and we need to change the type at a future point in time.

• Verify fields types are changed when LDD fields are reloaded #215

⚙ Engineering Details

• Potentially add functionality to registry-mgr create new re-indexed index with for new mappings to take affect
  • CLI prompt that this is a significant update and no other data should be loaded during this operation

[jordanpadams]

📆 01/2024 status: To be deferred. Will be reviewed with SWG

[jordanpadams]

Deferral approved per NASA-PDS/pds-swg#26

[jordanpadams]

📆 05/2024 status: In work. Start delayed 1 sprint due to delays in #185. No impact on build expected

[jordanpadams]

📆 06/2024 status: Start delayed and additional 2 sprints due to delays in #185. No impact on build expected. Not a critical task needed for this build.

[jordanpadams]

📆 07/2024 status: Start delayed an additional sprint due to delays in #185. No impact on build expected. Not a critical task needed for this build.

[jordanpadams]

📆 08/2024 status: Not a critical task needed for this build. Deferring to B15.1

[alexdunnjpl]

@jordanpadams was checking this intended to be part of the sweeper or not, in the end?

NASA-PDS/registry-sweepers#148

[jordanpadams]

@alexdunnjpl correct. NASA-PDS/registry-sweepers#148 basically does this. @tloubrieu-jpl were just talking about this and how it relates to LDDs missing from online, and how we can go back and clean that up in the future.

[alexdunnjpl]

@jordanpadams the in-progress fix for NASA-PDS/registry-sweepers#148 will populate missing mappings, but cannot (as initially conceived) fix a mapping which exists but has the wrong type.

We can support that in the first implementation, it will just mean doing additional work before the branch is PRd.

Let me know if you'd like me to front-load that feature, or do it later as an incremental update.

[jordanpadams]

@alexdunnjpl incremental update is fine. We will add this to up-next

[jordanpadams]

📆 10/2024: in work. on schedule

[jordanpadams]

📆 11/2024 status: Delayed multiple sprints due to differences between AOSS and vanilla OpenSearch. No impact on other tasks expected.