[
https://issues.apache.org/jira/browse/HDDS-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arafat Khan updated HDDS-11615:
-------------------------------
Description:
With Recon’s new schema versioning framework now integrated HDDS-11465, it is
essential to address initial schema constraints for existing tables.
Previously, Recon lacked schema versioning, which meant there were no upgrade
actions or mechanisms to adjust schema tables post-upgrade. This led to
inconsistencies, especially when new enum states (like {{MISSING}} and
{{NEGATIVE_SIZE}} in {{{}UnHealthyContainerStates{}}}) were introduced, as
older schema versions might still persist despite upgrades.
This ticket introduces a foundational upgrade action,
{{{}InitialConstraintUpgradeAction{}}}, associated with the *INITIAL_VERSION*
feature to handle any missed schema updates within the {{UNHEALTHY_CONTAINERS}}
table. This upgrade action retroactively applies constraints and ensures all
existing tables are correctly versioned. Moving forward, any updates or new
metadata table introductions in Recon will be tracked and managed by version
using the {{ReconLayoutFeature}} framework, enabling a seamless and structured
upgrade process for future schema changes
was:Following the integration of the Recon schema versioning framework
[HDDS-11465|https://issues.apache.org/jira/browse/HDDS-11465], this task
introduces a dedicated upgrade action to manage initial schema constraints
within the {{UNHEALTHY_CONTAINERS}} table. The upgrade action
{{InitialConstraintUpgradeAction}} is now responsible for adding or updating
constraints in the schema, isolating these operations from the core
initialization process. This ensures that constraint management aligns with the
upgrade framework and supports clean, versioned schema transitions in Recon.
> Add Upgrade Action for Initial Schema Constraints for Unhealthy Container
> Table in Recon
> ----------------------------------------------------------------------------------------
>
> Key: HDDS-11615
> URL: https://issues.apache.org/jira/browse/HDDS-11615
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Reporter: Arafat Khan
> Priority: Major
>
> With Recon’s new schema versioning framework now integrated HDDS-11465, it is
> essential to address initial schema constraints for existing tables.
> Previously, Recon lacked schema versioning, which meant there were no upgrade
> actions or mechanisms to adjust schema tables post-upgrade. This led to
> inconsistencies, especially when new enum states (like {{MISSING}} and
> {{NEGATIVE_SIZE}} in {{{}UnHealthyContainerStates{}}}) were introduced, as
> older schema versions might still persist despite upgrades.
> This ticket introduces a foundational upgrade action,
> {{{}InitialConstraintUpgradeAction{}}}, associated with the *INITIAL_VERSION*
> feature to handle any missed schema updates within the
> {{UNHEALTHY_CONTAINERS}} table. This upgrade action retroactively applies
> constraints and ensures all existing tables are correctly versioned. Moving
> forward, any updates or new metadata table introductions in Recon will be
> tracked and managed by version using the {{ReconLayoutFeature}} framework,
> enabling a seamless and structured upgrade process for future schema changes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
