[I] [VL] Translate Velox bitmap_construct_agg exceptions to Spark-native exception types [gluten]

["minni31 (via GitHub)" <gi...@apache.org>]

minni31 opened a new issue, #12238:
URL: https://github.com/apache/gluten/issues/12238

   ## Background
   
   When `bitmap_construct_agg` is offloaded to native Velox execution, invalid bitmap positions throw a `GlutenException` (wrapping `VeloxUserError`) instead of the expected `SparkArrayIndexOutOfBoundsException` with error condition `INVALID_BITMAP_POSITION`.
   
   ## Current State
   
   In PR #12142, we excluded the following error-path tests from `VeloxTestSettings` as a workaround:
   - `INVALID_BITMAP_POSITION: position out of bounds`
   - `INVALID_BITMAP_POSITION: negative position`
   
   These tests verify that Spark throws `SparkArrayIndexOutOfBoundsException` for out-of-bounds and negative positions in `bitmap_construct_agg`. Since Velox produces its own error format (`VeloxUserError`), the JVM receives a `GlutenException` instead.
   
   ## Expected Behavior
   
   The JVM-side error translation layer should detect Velox errors for invalid bitmap positions and re-throw them as `SparkArrayIndexOutOfBoundsException` with the appropriate `INVALID_BITMAP_POSITION` error condition, preserving Spark error API compatibility.
   
   ## References
   
   - PR: #12142
   - Error condition: `INVALID_BITMAP_POSITION` (introduced in Spark 3.5)
   - Relevant test: `QueryExecutionErrorsSuite` lines 952, 966


-- 
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: commits-unsubscribe@gluten.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@gluten.apache.org
For additional commands, e-mail: commits-help@gluten.apache.org