Skip to content

TEZ-4689: Introduce Node abstraction for DAGAppMaster instead of sepagrate NodeManager-related fields - #461

Merged
abstractdog merged 5 commits into
apache:masterfrom
Aggarwal-Raghav:TEZ-4689
Mar 13, 2026
Merged

TEZ-4689: Introduce Node abstraction for DAGAppMaster instead of sepagrate NodeManager-related fields#461
abstractdog merged 5 commits into
apache:masterfrom
Aggarwal-Raghav:TEZ-4689

Conversation

@Aggarwal-Raghav

Copy link
Copy Markdown
Contributor

No description provided.

private final int nmPort;
private final int nmHttpPort;
private String nmHost;
private int nmPort;

@Aggarwal-RaghavAggarwal-RaghavFeb 27, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nmPort is not used anywhere but still keeping getAppNMPort() public api

if (!isLocal) {
this.nmHost = nodeContext.getNodeHostString();
int nmHttpPort = Integer.parseInt(nodeContext.getNodeHttpPortString());
this.containerLogs =

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this.containerLogs is making use of nmHttpPort and nmHost, moved it from constructor to serviceInit() and made nmHttpPort as local variable

DAGProtos.ConfigurationProto confProto = amExtensions.loadConfigurationProto();
TezUtilsInternal.addUserSpecifiedTezConfiguration(conf, confProto.getConfKeyValuesList());

NodeContext nodeContext = new YarnNodeManagerContext();

@Aggarwal-RaghavAggarwal-RaghavFeb 27, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to wrap in if statement for checking if framework is yarn. As the YarnNodeManagerContext is using supplier it won't be evaluated immediately and evaluation will happen only it !isLocal.
NOTE: in tez-am docker image tez.local.mode = true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should assume that tez.local.mode is going to become false with this whole initiative eventually, when reaching the optimal state of separate AM and Task containers

@tez-yetus

This comment was marked as outdated.

@tez-yetus

This comment was marked as outdated.

Comment threadtez-dag/src/main/java/org/apache/tez/dag/app/DAGAppMaster.java Outdated
@Aggarwal-Raghav
Aggarwal-Raghav marked this pull request as ready for review February 28, 2026 17:13
@tez-yetus

This comment was marked as outdated.

Comment threadtez-dag/src/main/java/org/apache/tez/dag/app/LocalNodeContext.java Outdated
Comment threadtez-dag/src/main/java/org/apache/tez/dag/app/DAGAppMaster.java Outdated
@tez-yetus

This comment was marked as outdated.

// Install the tez class loader, which can be used add new resources
TezClassLoader.setupTezClassLoader();
Thread.setDefaultUncaughtExceptionHandler(new YarnUncaughtExceptionHandler());
final String pid = System.getenv().get("JVM_PID");

@abstractdogabstractdogMar 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while I like using ProcessHandle instead of JVM_PID, I'm not sure if this is 100% correct
I'm concerned by the fact that JVM_PID is used in yarn too, see in hadoop code, e.g. https://github.com/apache/hadoop/blob/f49c49aa083b9324ae432902f94a7aaf98f543ea/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapred/YarnChild.java#L126

also, not 100% sure if JVM_PID belongs to the actual Java process id or the launch_container.sh shell script provided by yarn: even if the shell script must be the parent of the jvm process, they are not the same

@Aggarwal-RaghavAggarwal-RaghavMar 4, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll investigate on this and get back to you on this.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So i tested by putting both

LOG.info("######");
LOG.info("System.getenv().get(\"JVM_PID\") value is: {}", old_pid);
LOG.info("ProcessHandle.current().pid() value is : {}", pid);
LOG.info("######");

the JVM_PID belongs to launch_container.sh and
ProcessHandler one is DagAppMaster

Screenshot confirming the same.
Screenshot 2026-03-04 at 11 52 14 PM
Screenshot 2026-03-04 at 11 49 46 PM

Will revert this change. Thanks for pointing this!!

Comment on lines +1214 to +1219
public int getAppNMPort() {
return nmPort;
return nodeContext.getNodePort();
}

public int getAppNMHttpPort() {
return nmHttpPort;
return nodeContext.getNodeHttpPort();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a chance we can remove getAppNMPort and getAppNMHttpPort methods altogether?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i thought so but they are public api, but its a tez major version change so we can do so. I wanted to discuss the same with you. Let me know.
there are few variables that can be made final and local to method instead of class varaibles in DagAppMaster. I wanted to clean that up and use JDK 21 features like enhanced switch but the change would have been outside the scope of PR. I can create a separte PR for code hygiene?

@abstractdogabstractdogMar 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code hygiene patches are always welcome
IMO you can remove these methods here, and do more in separate PRs

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure. will update PR shortly and raise separate JIRA/PR for code hygiene. Thanks

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 18sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
+1 💚test4tests0m 0sThe patch appears to include 4 new or modified test files.
_ master Compile Tests _
+1 💚mvninstall10m 59smaster passed
+1 💚compile0m 43smaster passed
+1 💚checkstyle1m 6smaster passed
+1 💚javadoc0m 36smaster passed
+0 🆗spotbugs2m 22stez-dag in master has 749 extant spotbugs warnings.
_ Patch Compile Tests _
+1 💚mvninstall0m 31sthe patch passed
+1 💚codespell0m 51sNo new issues.
+1 💚compile0m 30sthe patch passed
+1 💚javac0m 30sthe patch passed
+1 💚blanks0m 0sThe patch has no blanks issues.
-0 ⚠️checkstyle0m 10s/buildtool-patch-checkstyle-tez-dag.txtThe patch fails to run checkstyle in tez-dag
+1 💚javadoc0m 13sthe patch passed
+1 💚spotbugs1m 44sthe patch passed
_ Other Tests _
+1 💚unit5m 58stez-dag in the patch passed.
+1 💚asflicense0m 13sThe patch does not generate ASF License warnings.
27m 37s
SubsystemReport/Notes
DockerClientAPI=1.53 ServerAPI=1.53 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/5/artifact/out/Dockerfile
GITHUB PR#461
Optional Testsdupname asflicense javac javadoc unit spotbugs checkstyle codespell detsecrets compile
unameLinux 3e7149cc127d 5.15.0-160-generic #170-Ubuntu SMP Wed Oct 1 10:06:56 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/.yetus/personality.sh
git revisionmaster / b882a0c
Default JavaUbuntu-21.0.10+7-Ubuntu-124.04
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/5/testReport/
Max. process+thread count262 (vs. ulimit of 5500)
modulesC: tez-dag U: tez-dag
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/5/console
versionsgit=2.43.0 maven=3.8.7 spotbugs=4.9.3 codespell=2.4.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@abstractdog

abstractdog commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

hm, how is this possible:
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/5/artifact/out/buildtool-patch-checkstyle-tez-dag.txt

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project tez-dag: An error has occurred in Checkstyle report generation. Failed during checkstyle configuration: Exception was thrown while processing /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/tez-dag/src/main/java/org/apache/tez/dag/app/NodeContext.java: IllegalStateException occurred while parsing file /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/tez-dag/src/main/java/org/apache/tez/dag/app/NodeContext.java. /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/tez-dag/src/main/java/org/apache/tez/dag/app/NodeContext.java:18:8: unexpected token: sealed -> [Help 1]

I thought sealed interfaces are present since JDK17, so that must not be a problem...however, it compiled successfully, but the checkstyle:checkstyle target was the one that failed, I hope the same can be reproduced locally

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

hm, how is this possible: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/5/artifact/out/buildtool-patch-checkstyle-tez-dag.txt

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project tez-dag: An error has occurred in Checkstyle report generation. Failed during checkstyle configuration: Exception was thrown while processing /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/tez-dag/src/main/java/org/apache/tez/dag/app/NodeContext.java: IllegalStateException occurred while parsing file /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/tez-dag/src/main/java/org/apache/tez/dag/app/NodeContext.java. /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/tez-dag/src/main/java/org/apache/tez/dag/app/NodeContext.java:18:8: unexpected token: sealed -> [Help 1]

I thought sealed interfaces are present since JDK17, so that must not be a problem...however, it compiled successfully, but the checkstyle:checkstyle target was the one that failed, I hope the same can be reproduced locally

I'm doing some investigation on checkstyle issue as part of #462 . but using checkstyle 3.6.0 and removing puppycrawler explicit dependency, then its working.

NodeContext nodeContext =
(frameworkService instanceof YarnServerFrameworkService)
? new YarnNodeManagerContext()
: null;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think instead of an instanceof check we should let ServerFrameworkService interface handle this: the advantage of separate framework service implementations is to eliminate these type checks (the ZkStandaloneServerFrameworkService can simply return null or a LocalNodeContext with dummy values)

}

@Override
public String getNodeHostString() {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could this be nodeHost? I believe "String" doesn't add any value here, it could be eliminated from variable names as well as interface

Comment on lines +29 to +31
private final Supplier<String> nodeHostStringSupplier;
private final Supplier<Integer> nodePortStringSupplier;
private final Supplier<Integer> nodeHttpPortStringSupplier;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can also remove "Supplier" suffix from the variable names: by looking at the variables, it should be clear that they are Suppliers

@abstractdog

abstractdog commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

@Aggarwal-Raghav : left some minor comments, but this looks good so far

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

@Aggarwal-Raghav : left some minor comments, but this looks good so far

Thanks! Will update PR I'm some time.

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 15sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
+1 💚test4tests0m 0sThe patch appears to include 4 new or modified test files.
_ master Compile Tests _
+1 💚mvninstall11m 5smaster passed
+1 💚compile0m 44smaster passed
+1 💚checkstyle1m 2smaster passed
+1 💚javadoc0m 37smaster passed
+0 🆗spotbugs2m 22stez-dag in master has 749 extant spotbugs warnings.
_ Patch Compile Tests _
+1 💚mvninstall0m 31sthe patch passed
+1 💚codespell0m 52sNo new issues.
+1 💚compile0m 32sthe patch passed
+1 💚javac0m 32sthe patch passed
+1 💚blanks0m 0sThe patch has no blanks issues.
-0 ⚠️checkstyle0m 11s/buildtool-patch-checkstyle-tez-dag.txtThe patch fails to run checkstyle in tez-dag
+1 💚javadoc0m 13sthe patch passed
+1 💚spotbugs1m 41sthe patch passed
_ Other Tests _
+1 💚unit6m 2stez-dag in the patch passed.
+1 💚asflicense0m 13sThe patch does not generate ASF License warnings.
27m 41s
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/6/artifact/out/Dockerfile
GITHUB PR#461
Optional Testsdupname asflicense javac javadoc unit spotbugs checkstyle codespell detsecrets compile
unameLinux b39160e6b376 5.15.0-160-generic #170-Ubuntu SMP Wed Oct 1 10:06:56 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/.yetus/personality.sh
git revisionmaster / 86675af
Default JavaUbuntu-21.0.10+7-Ubuntu-124.04
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/6/testReport/
Max. process+thread count217 (vs. ulimit of 5500)
modulesC: tez-dag U: tez-dag
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/6/console
versionsgit=2.43.0 maven=3.8.7 spotbugs=4.9.3 codespell=2.4.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@abstractdog

Copy link
Copy Markdown
Contributor

@Aggarwal-Raghav : this patch looks good to me, I'm just wondering if you found the root cause of the checkstyle problem and it can be proved that it's going to go away soon and precommit remains in a good shape

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

@Aggarwal-Raghav : this patch looks good to me, I'm just wondering if you found the root cause of the checkstyle problem and it can be proved that it's going to go away soon and precommit remains in a good shape

The puppycrawler checkstyle 8.35 (Jul 26, 2020) is before jdk17 (September 14, 2021) was launched, hence this error. Upgrading checkstyle version to 3.6.0 will help.

@abstractdog

Copy link
Copy Markdown
Contributor

@Aggarwal-Raghav : this patch looks good to me, I'm just wondering if you found the root cause of the checkstyle problem and it can be proved that it's going to go away soon and precommit remains in a good shape

The puppycrawler checkstyle 8.35 (Jul 26, 2020) is before jdk17 (September 14, 2021) was launched, hence this error. Upgrading checkstyle version to 3.6.0 will help.

thanks, good to know! can you create a Jira + PR about that to unblock this one? that would help a lot in modernizing Tez precommit infrastructure with a simple patch

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

@Aggarwal-Raghav : this patch looks good to me, I'm just wondering if you found the root cause of the checkstyle problem and it can be proved that it's going to go away soon and precommit remains in a good shape

The puppycrawler checkstyle 8.35 (Jul 26, 2020) is before jdk17 (September 14, 2021) was launched, hence this error. Upgrading checkstyle version to 3.6.0 will help.

thanks, good to know! can you create a Jira + PR about that to unblock this one? that would help a lot in modernizing Tez precommit infrastructure with a simple patch

sure.

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec7m 58sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
+1 💚test4tests0m 0sThe patch appears to include 4 new or modified test files.
_ master Compile Tests _
+1 💚mvninstall10m 19smaster passed
+1 💚compile0m 44smaster passed
+1 💚checkstyle1m 27smaster passed
+1 💚javadoc0m 37smaster passed
+0 🆗spotbugs2m 1stez-dag in master has 749 extant spotbugs warnings.
_ Patch Compile Tests _
+1 💚mvninstall0m 31sthe patch passed
+1 💚codespell0m 51sNo new issues.
+1 💚compile0m 30sthe patch passed
+1 💚javac0m 30sthe patch passed
+1 💚blanks0m 0sThe patch has no blanks issues.
-0 ⚠️checkstyle0m 24s/results-checkstyle-tez-dag.txttez-dag: The patch generated 10 new + 278 unchanged - 5 fixed = 288 total (was 283)
+1 💚javadoc0m 13sthe patch passed
+1 💚spotbugs1m 44sthe patch passed
_ Other Tests _
+1 💚unit5m 35stez-dag in the patch passed.
+1 💚asflicense0m 13sThe patch does not generate ASF License warnings.
34m 29s
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/7/artifact/out/Dockerfile
GITHUB PR#461
Optional Testsdupname asflicense javac javadoc unit spotbugs checkstyle codespell detsecrets compile
unameLinux 53e0dbc7b32b 5.15.0-160-generic #170-Ubuntu SMP Wed Oct 1 10:06:56 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/.yetus/personality.sh
git revisionmaster / 8203171
Default JavaUbuntu-21.0.10+7-Ubuntu-124.04
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/7/testReport/
Max. process+thread count231 (vs. ulimit of 5500)
modulesC: tez-dag U: tez-dag
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/7/console
versionsgit=2.43.0 maven=3.8.7 spotbugs=4.9.3 codespell=2.4.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

@abstractdog , this is ready. checkstyle is running now.

@abstractdog

abstractdog commented Mar 11, 2026

Copy link
Copy Markdown
Contributor

@abstractdog , this is ready. checkstyle is running now.

https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/7/artifact/out/results-checkstyle-tez-dag.txt
"Line is longer " kind of alerts are new, can you please fix them? the rest looks okay, e.g. ParameterNumber was just improved here, because you replaced 3 params with a context

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

@abstractdog , this is ready. checkstyle is running now.

https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/7/artifact/out/results-checkstyle-tez-dag.txt "Line is longer " kind of alerts are new, can you please fix them? the rest looks okay, e.g. ParameterNumber was just improved here, because you replaced 3 params with a context

Will use intelliJ-google-java-format. Initially, I didn't do it because it is causing diff issue in github because of formatting, making difficult to review.

@abstractdog
abstractdog self-requested a review March 11, 2026 12:31

@abstractdogabstractdog left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pending tests

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 16sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
+1 💚test4tests0m 0sThe patch appears to include 4 new or modified test files.
_ master Compile Tests _
+1 💚mvninstall10m 22smaster passed
+1 💚compile0m 45smaster passed
+1 💚checkstyle1m 24smaster passed
+1 💚javadoc0m 35smaster passed
+0 🆗spotbugs2m 4stez-dag in master has 749 extant spotbugs warnings.
_ Patch Compile Tests _
+1 💚mvninstall0m 32sthe patch passed
+1 💚codespell0m 51sNo new issues.
+1 💚compile0m 31sthe patch passed
+1 💚javac0m 31sthe patch passed
+1 💚blanks0m 0sThe patch has no blanks issues.
-0 ⚠️checkstyle0m 24s/results-checkstyle-tez-dag.txttez-dag: The patch generated 2 new + 279 unchanged - 4 fixed = 281 total (was 283)
+1 💚javadoc0m 14sthe patch passed
+1 💚spotbugs1m 43sthe patch passed
_ Other Tests _
+1 💚unit6m 21stez-dag in the patch passed.
+1 💚asflicense0m 14sThe patch does not generate ASF License warnings.
27m 36s
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/8/artifact/out/Dockerfile
GITHUB PR#461
Optional Testsdupname asflicense javac javadoc unit spotbugs checkstyle codespell detsecrets compile
unameLinux ceebfe522922 5.15.0-160-generic #170-Ubuntu SMP Wed Oct 1 10:06:56 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-461/src/.yetus/personality.sh
git revisionmaster / c6aaa2f
Default JavaUbuntu-21.0.10+7-Ubuntu-124.04
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/8/testReport/
Max. process+thread count249 (vs. ulimit of 5500)
modulesC: tez-dag U: tez-dag
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-461/8/console
versionsgit=2.43.0 maven=3.8.7 spotbugs=4.9.3 codespell=2.4.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

is there any way to re-trigger the Github Actions without pushing the changes again?

@abstractdog

Copy link
Copy Markdown
Contributor

is there any way to re-trigger the Github Actions without pushing the changes again?

I just retriggered them

@abstractdog
abstractdog merged commit 9725e38 into apache:masterMar 13, 2026
5 of 12 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@Aggarwal-Raghav@tez-yetus@abstractdog