Skip to content

[AURON #2102] Initializing JavaClasses in JNI and decoupling Spark#2103

Merged
Tartarus0zm merged 4 commits intoapache:masterfrom
Tartarus0zm:jni-decoupled-with-spark
Mar 18, 2026
Merged

[AURON #2102] Initializing JavaClasses in JNI and decoupling Spark#2103
Tartarus0zm merged 4 commits intoapache:masterfrom
Tartarus0zm:jni-decoupled-with-spark

Conversation

@Tartarus0zm
Copy link
Contributor

Which issue does this PR close?

Closes #2102

Rationale for this change

Many fields in JavaClasses are tightly coupled with Spark Java code; we decide whether to load the relevant code based on the engine.

What changes are included in this PR?

  • Introduce getEngineName API for JniBridge and AuronAdaptor
  • modify jni_bridge add engine type checking when initializing JavaClasses

Are there any user-facing changes?

  • No

How was this patch tested?

  • No

@Tartarus0zm
Copy link
Contributor Author

The engine name has been successfully retrieved.
2026-03-18 11:49:12.018 (+0.000s) [INFO] [auron_jni_bridge::jni_bridge:496] (stage: 0, partition: 0, tid: 0) - Runtime engine is Spark

@Tartarus0zm
Copy link
Contributor Author

@richox CI is Green, PTAL

@Tartarus0zm Tartarus0zm merged commit 5998f1c into apache:master Mar 18, 2026
116 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Initializing JavaClasses in JNI and decoupling Spark

2 participants