You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Abhishek Pal (Jira)" <ji...@apache.org> on 2024/12/03 07:27:00 UTC

[jira] [Created] (HDDS-11846) [Recon] Recon Schema version_number column is always set as -1

Abhishek Pal created HDDS-11846:
-----------------------------------

             Summary: [Recon] Recon Schema version_number column is always set as -1
                 Key: HDDS-11846
                 URL: https://issues.apache.org/jira/browse/HDDS-11846
             Project: Apache Ozone
          Issue Type: Bug
          Components: Ozone Recon
    Affects Versions: 2.0.0
            Reporter: Abhishek Pal
            Assignee: Arafat Khan


Recon Schema version was introduced as a part of [HDDS-11465|https://issues.apache.org/jira/browse/HDDS-11465] as a part of which we modify recon tables which might have changed in a later version in case of an upgrade.

Currently the MetadataLayoutVersion is always set to -1 causing the upgrade handler to run even for fresh installs.
This is coming from [ReconSchemaVersionTableManager#getCurrentSchemaVersion()|https://github.com/apache/ozone/blob/77ce962f3471383e4d3fa9abae79bde8dbfd9faf/hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/ReconSchemaVersionTableManager.java#L56].

We should set this column to the version of the current code so that the upgrade handler doesn't run in case of a fresh install.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org