Add typoed name DataPropagationLatencyGuage as deprecated #517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues
Name DataPropagationLatencyGauge has a typo #512
If we remove the typoed name DataPropagationLatencyGuage, current metrics graph may not see the metric and historical DataPropagationLatencyGuage data may be lost. To solve the problem, we need to add back DataPropagationLatencyGuage and set it as deprecated.
Description
If we remove the typoed name DataPropagationLatencyGuage, current metrics graph may not see the metric and historical DataPropagationLatencyGuage data may be lost. To solve the problem, we need to add back DataPropagationLatencyGuage and set it as deprecated.
Tests
[] The following tests are written for this issue:
(List the names of added unit/integration tests)
The following is the result of the "mvn test" command on the appropriate module:
Tests all pass.
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] TestPartitionLevelTransitionConstraint.test:160 expected: but was:
[ERROR] TestTaskPerformanceMetrics.testTaskPerformanceMetrics:118 expected: but was:
[INFO]
[ERROR] Tests run: 882, Failures: 2, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 53:55 min
[INFO] Finished at: 2019-10-21T22:41:58-07:00
END TestPartitionLevelTransitionConstraint_test at Mon Oct 21 22:47:22 PDT 2019
END test at Mon Oct 21 22:47:22 PDT 2019, took: 1650ms.
Shut down zookeeper at port 2183 in thread main
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.305 s - in org.apache.helix.integration.TestPartitionLevelTransitionConstraint
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
TestTaskPerformanceMetrics#testTaskPerformanceMetrics
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.152 s - in org.apache.helix.monitoring.mbeans.TestTaskPerformanceMetrics
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
Commits
My commits all reference appropriate Apache Helix GitHub issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"
Documentation
In case of new functionality, my PR adds documentation in the following wiki page:
(Link the GitHub wiki you added)
Code Quality