Zhengcy05 opened a new pull request, #10509:
URL: https://github.com/apache/rocketmq/pull/10509

   <!-- Please make sure the target branch is right. In most case, the target 
branch should be `develop`. -->
   
   ### Which Issue(s) This PR Fixes
   
   <!-- Please ensure that the related issue has already been created, and 
[link this pull request to that issue using 
keywords](<https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword>)
 to ensure automatic closure. -->
   Fixes #10434
   
   - Fixes #issue_id
   
   ### Brief Description
   
   <!-- Write a brief description for your pull request to help the maintainer 
understand the reasons behind your changes. -->
   This PR implements the v5 gRPC QueryOffset and GetOffset RPCs in the proxy.
   Previously, these RPCs were declared by the proto service but were not 
overridden by the proxy gRPC service implementation, so clients received 
UNIMPLEMENTED.
   The change adds a new OffsetActivity, wires it through the gRPC 
activity/application layers, and maps:
   - GetOffset to consumer offset query
   - QueryOffset(BEGINNING) to min offset
   - QueryOffset(END) to max offset
   - QueryOffset(TIMESTAMP) to timestamp-based offset search
   It also exposes searchOffset through the proxy processor/message service 
layers so the timestamp policy can reuse the existing broker remoting 
capability.
   
   ### How Did You Test This Change?
   ```bash
   env JAVA_HOME=/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home 
mvn -pl proxy -Dspotbugs.skip=true 
-Dtest=OffsetActivityTest,GrpcMessagingApplicationTest -DfailIfNoTests=false 
test
   ```
   
   <!-- In order to ensure the code quality of Apache RocketMQ, we expect every 
pull request to have undergone thorough testing. -->
   


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

Reply via email to