taiyang-li opened a new pull request, #12376:
URL: https://github.com/apache/gluten/pull/12376

   ## What changes were proposed in this pull request?
   
   This patch extends the JNI bridge between the Java/Scala layer and the 
native C++ layer to propagate Spark task-level identification information:
   
   - **RuntimeJniWrapper.createRuntime**: Added `long taskAttemptId` parameter
   - **NativeMemoryManagerJniWrapper.create**: Added `String name` (pool name) 
parameter
   - **NativeMemoryManagerJniWrapper.hold**: Added `String name` and `long 
taskAttemptId` parameters
   - **NativeMemoryManagerJniWrapper.release**: Added `long taskAttemptId` 
parameter
   
   On the native C++ side:
   - `Runtime` gains a `taskAttemptId_` member with getter/setter
   - `MemoryManager` gains a `name_` member with getter/setter
   
   The values are set via setters after object creation, so **no changes are 
needed for existing backend subclasses** (Velox, ClickHouse). The Factory 
typedefs and constructor signatures remain unchanged.
   
   This makes per-task diagnostics and per-pool logging possible, and unblocks 
future backends (e.g. Bolt) that need task-level identification at the native 
layer.
   
   ## How was this patch tested?
   
   - Static verification: All JNI method signatures match between Java and C++ 
(parameter count and types verified).
   - No changes to Velox/CH backend code - all existing subclasses compile 
unchanged.
   - The patch is purely additive (new members + getters/setters), with no 
behavioral changes for existing backends.
   - Full build verification is pending; this is a minimal infrastructure patch.
   
   ## Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude claude-sonnet-4-6


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to