You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Swaminathan Balachandran (Jira)" <ji...@apache.org> on 2022/06/03 19:24:00 UTC
[jira] [Updated] (HDDS-6489) Check cleanup tables for each OM response
[ https://issues.apache.org/jira/browse/HDDS-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swaminathan Balachandran updated HDDS-6489:
-------------------------------------------
Summary: Check cleanup tables for each OM response (was: Unit test to check cleanup tables for each OM response)
> Check cleanup tables for each OM response
> -----------------------------------------
>
> Key: HDDS-6489
> URL: https://issues.apache.org/jira/browse/HDDS-6489
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Manager
> Reporter: Ethan Rose
> Assignee: Swaminathan Balachandran
> Priority: Minor
> Labels: newbie, pull-request-available
>
> OM response classes need to declare the tables they act on in the @CleanupTableInfo annotation. Sometimes when responses are updated with new tables, this annotation is not also updated, as seen in HDDS-6480. This Jira proposes adding a unit test to the existing TestCleanupTableInfo class that would:
> 1. Use reflection to identify all the OM responses.
> - An example of this is already in the existing unit test.
> 2. Call addToDBBatch for each response with a mock OMMetadataManager instance.
> 3. Check that the list of tables accessed in the mock match the list of tables in the response's annotation.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org