ReemaAlzaid opened a new pull request, #13449:
URL: https://github.com/apache/gluten/pull/13449

   <!--
   Thank you for submitting a pull request! Here are some tips:
   
   1. For first-time contributors, please read our contributing guide:
      https://github.com/apache/gluten/blob/main/CONTRIBUTING.md
   2. If necessary, create a GitHub issue for discussion beforehand to avoid 
duplicate work.
   3. If the PR is specific to a single backend, include [VL] or [CH] in the PR 
title to indicate the
      Velox or ClickHouse backend, respectively.
   4. If the PR is not ready for review, please mark it as a draft.
   -->
   
   ## What changes are proposed in this pull request?
   
   <!--
   Provide a clear and concise description of the changes introduced in this PR.
   Ensure the PR description aligns with the code changes, especially after 
updates.
   If applicable, include "Fixes #<GitHub_Issue_ID>" to automatically close the 
corresponding issue
   when the PR is merged.
   -->
   The native Kafka reader can request a 100 ms consume wait even when less
   time remains in the configured poll timeout.
   
   Cap each consume wait by the remaining poll budget. For example, when
   only 10 ms remain, request a 10 ms wait instead of 100 ms.
   
   ## How was this patch tested?
   
   <!--
   Describe how the changes were tested, if applicable.
   Include new tests to validate the functionality, if necessary.
   For UI-related changes, attach screenshots to demonstrate the updates.
   -->
   On Ubuntu ARM64
   
   - Native Kafka connector: 14/14 tests passed, including 6 timeout tests.
   - Generic Spark 3.5.5/JNI: 6/6 VeloxLiteralSuite tests passed.
   - Spark streaming against a real Kafka 3.9.1 broker: successfully read
     and verified records 1, 2, and 3 using Spark’s Java Kafka reader.
   
   The timeout tests cover exact consume timeout arguments, successive
   waits sharing the poll budget, nonblocking reads after collecting records,
   and preserving collected records when the budget expires
   
   ## Was this patch authored or co-authored using generative AI tooling?
   
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   


-- 
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