AMBARI-26142: JDK17 support for Ambari-metrics#134
Merged
Conversation
Co-authored-by: Mohammad Arshad <arshad@apache.org>
sandeepk318
force-pushed
the
MetricsJDK17
branch
from
c790a47 to
72feffc
Compare
Contributor
|
@sandeep318kumar |
Contributor
|
@sandeep318kumar It looks like three tests have failed. Could you please fix them? |
Contributor
|
@sandeep318kumar It will be merged first, and the failed unit tests will be submitted in a separate PR. |
JiaLiangC
changed the title
Contributor
Author
|
@JiaLiangC Can I work on these test cases? |
Contributor
@sandeep318kumar sorry for later reply, of course you can. |
JiaLiangC
added a commit
that referenced
this pull request
Mar 15, 2025
This reverts commit 667fa9a.
JiaLiangC
added a commit
that referenced
this pull request
Mar 15, 2025
This reverts commit 667fa9a.
JiaLiangC
added a commit
to JiaLiangC/ambari-metrics
that referenced
this pull request
Mar 20, 2025
* master: AMBARI-26327: Fix ambari-metrics-monitor start failure (apache#143) Revert "AMBARI-26142: JDK17 support for Ambari-metrics (apache#134)" (apache#142) AMBARI-26264. Disable releases for apache.snapshots repo (apache#138) AMBARI-25954 Upgrade ignite-core to 2.1.0 to 2.15.0 (apache#114) [AMBARI-26184] Resolve snakeyaml 0.12 CVE (apache#136) AMBARI-26142: JDK17 support for Ambari-metrics (apache#134) [AMBARI-26135] Upgrade net.sf.ehcache to 3.10.0 (apache#132) status: command not found (apache#125) [AMBARI-26095] Upgrade Grafana version 9.5.5 to 11.1.4 (apache#129) [AMBARI-26134]Resolve Test case failures in Ambari Metrics host Monitoring (apache#133) AMBARI-26123：Ambari-metrics build failed apache#130 AMBARI-26020: upgrade Ambari Metrics to python3 (apache#126) AMBARI-25998: Host uuid is not getting synced to other collectors, causing NPE while accessing metric (apache#124)
jojochuang
pushed a commit
to jojochuang/ambari-metrics
that referenced
this pull request
Apr 21, 2025
Co-authored-by: Mohammad Arshad <arshad@apache.org>
jojochuang
pushed a commit
to jojochuang/ambari-metrics
that referenced
this pull request
Apr 21, 2025
…pache#142) This reverts commit 667fa9a.
|
Hi @JiaLiangC we would need the JDK-17 support in Ambari metrics to enable helix-core fix #173 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
[AMBARI-26142] JDK17 support for Ambari-metrics
What changes were proposed in this pull request?
upgrade maven-compiler-plugin to 3.5
maven-shade-plugin to 3.5.1
guava to 32.1.3-jre
maven-surefire-plugin to 3.2.5
JDK to 17
API changes
tests cases modified
(Please fill in changes proposed in this fix)
How was this patch tested?
TESTING is pending.
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)
Please review Ambari Contributing Guide before opening a pull request.