[
https://issues.apache.org/jira/browse/HDDS-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arafat Khan updated HDDS-11465:
-------------------------------
Summary: Introducing Schema Versioning for Recon Derby table to Handle
Fresh Installs and Upgrades (was: Schema Versioning Enhancement for Recon
Derby table to Handle Fresh Installs and Upgrades)
> Introducing Schema Versioning for Recon Derby table to Handle Fresh Installs
> and Upgrades
> -----------------------------------------------------------------------------------------
>
> Key: HDDS-11465
> URL: https://issues.apache.org/jira/browse/HDDS-11465
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Affects Versions: 1.4.0
> Reporter: Arafat Khan
> Assignee: Arafat Khan
> Priority: Major
>
> Currently, Recon does not have a schema versioning mechanism in place for
> handling database schema evolution. As a result, when new schema changes are
> introduced (e.g., adding new enum states like {{{}MISSING{}}},
> {{NEGATIVE_SIZE}} in the {{{}UnHealthyContainerStates{}}}) for the
> {*}{{UnHealthyContainerTable}}{*}, it becomes challenging to distinguish
> between fresh installations and upgrades, leading to issues where old schema
> versions may still be used despite an upgrade.
> This ticket proposes introducing a *schema versioning system* to manage
> database schema changes in a more controlled manner
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
