-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-29815: Fix issue where backup integration tests are not running in IntelliJ #7625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HBASE-29815: Fix issue where backup integration tests are not running in IntelliJ #7625
Conversation
… in IntelliJ Change-Id: I467b73cd736d72c198d9314feea10dc6baa8af9b
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request fixes an issue where backup integration tests (IntegrationTestBackupRestore and IntegrationTestContinuousBackupRestore) fail to initialize essential test parameters when run via IntelliJ or Maven, though they work correctly when executed via the bin/hbase command-line tool.
Changes:
- Initialized static test parameter variables with sentinel value
-1to enable detection of uninitialized state - Added
initializeTestParameters()method to ensure test parameters are properly initialized from configuration when not set via command-line - Refactored
setUp()methods in concrete test classes to use the new initialization method
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| IntegrationTestBackupRestoreBase.java | Added sentinel initialization for static test parameters, created initializeTestParameters() method, removed unused variables, capitalized comment, and added missing import |
| IntegrationTestBackupRestore.java | Replaced direct util and conf initialization with call to initializeTestParameters() |
| IntegrationTestContinuousBackupRestore.java | Replaced direct util and conf initialization with call to initializeTestParameters() |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
hbase-it/src/test/java/org/apache/hadoop/hbase/backup/IntegrationTestBackupRestoreBase.java
Outdated
Show resolved
Hide resolved
hbase-it/src/test/java/org/apache/hadoop/hbase/backup/IntegrationTestBackupRestoreBase.java
Outdated
Show resolved
Hide resolved
hbase-it/src/test/java/org/apache/hadoop/hbase/backup/IntegrationTestBackupRestoreBase.java
Outdated
Show resolved
Hide resolved
Change-Id: Iac0de197dde0bc4b392ebe839b4619bc5ba68383
taklwu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the update, LGTM
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
https://issues.apache.org/jira/browse/HBASE-29815
This pull request fixes an issue where
IntegrationTestContinuousBackupRestoreandIntegrationTestBackupRestoreare able to run in the command line usingbin/hbase, but they will not run in IntelliJ for in the command line using Maven. This issue is fixed by ensuring essential class variables for the integration tests are initialized, regardless of how the test is executed.Note:
IntegrationTestContinuousBackupRestoreandIntegrationTestBackupRestorewill still fail on this branch for different reasons due to HBASE-29825 and HBASE-29826.