Fixes #19944: updates operations to point to new tables

[heamioh]

Describe your changes:

Fixes Issue #19944

I worked on fixing the OpenMetadata info(), validate(), repair(), and checkConnection() operations because they used to reference only the old tables (DATABASE_CHANGE_LOG, via flyway) and not the new tables (SERVER_MIGRATION_SQL_LOGS and SERVER_CHANGE_LOGS). With the new changes, all the openmetadata-ops.sh commands now include functionality to handle the new tables. I tested these changes using unit tests, which I have included in the OpenMetadataOperationsTest.java file.

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Bug fix

• I have added a test that covers the exact scenario we are fixing. For complex issues, comment the issue number in the test for future reference.

---

Summary by Gitar

• New CLI operations:
  • info command displays native migration status from SERVER_CHANGE_LOG with metrics
  • validate command checks for pending/failed migrations via MigrationWorkflow.validateMigrationsForServer()
  • repair command removes failed entries from SERVER_CHANGE_LOG and SERVER_MIGRATION_SQL_LOGS
• Enhanced operation:
  • checkConnection now verifies access to native migration tables alongside existing checks

_{This will update automatically on new commits.}

---

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[github-actions]

The Java checkstyle failed.

Please run mvn spotless:apply in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Java code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[mohityadav766]

@heamioh changes looks good, once checks passes will merge it in

[github-actions]

The Java checkstyle failed.

Please run mvn spotless:apply in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Java code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions]

The Java checkstyle failed.

Please run mvn spotless:apply in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Java code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions]

The Java checkstyle failed.

Please run mvn spotless:apply in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Java code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions]

The Java checkstyle failed.

Please run mvn spotless:apply in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Java code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[gitar-bot]

Rules 🎸 1 action taken

Gitar Rules

🎸 Summary Enhancement: Added technical summary to merged PR documenting new CLI operations

_{2 rules not applicable. Show all rules by commenting gitar display:verbose.}

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}