mcvsubbu opened a new pull request #5486:
URL: https://github.com/apache/incubator-pinot/pull/5486


   …gOffset
   
   Updated the segment commit protocol so that new element 
streamPartitionMsgOffset
   is populated in requests (as request parameters) and in response (as JSON 
string element)
   
   The server side has been modified to send the 'streamPartitionMsgOffset' as 
well as we the
   'offset' parameters to the controller. The controller looks for and prefers 
streamPartitionMsgOffset
   but falls back to offset if the streamPartitionMsgOffset is not there.
   
   The controller side, in the repsonse message, populates both of the 
elements, and the server on
   the receiver side does likewise -- preferring streamPartitionMsgOffset.
   
   All callers into the protocol module have been modified to NOT set the 
offset field. Instead,
   only set the streamPartitionMsgOffset field. The 'offset' value will be 
derived from
   streamPartitionMsgOffset.
   
   Added a test to make sure that the controller always generates both 
elements. Such a test was not
   possible in the server side at this time, so verified manually.
   
   Manually ran LLCClusterIntergrationTest by disabling populating 
`streamPartitionMsgOffset` on the
   server side (old server/new controller) and on the controller respons side 
(new server/old controller)
   
   Issue #5359
   
   ## Description
   Add a description of your PR here.
   A good description should include pointers to an issue or design document, 
etc.
   ## Upgrade Notes
   Does this PR prevent a zero down-time upgrade? (Assume upgrade order: 
Controller, Broker, Server, Minion)
   * [ ] Yes (Please label as **<code>backward-incompat</code>**, and complete 
the section below on Release Notes)
   
   Does this PR fix a zero-downtime upgrade introduced earlier?
   * [ ] Yes (Please label this as **<code>backward-incompat</code>**, and 
complete the section below on Release Notes)
   
   Does this PR otherwise need attention when creating release notes? Things to 
consider:
   - New configuration options
   - Deprecation of configurations
   - Signature changes to public methods/interfaces
   - New plugins added or old plugins removed
   * [ ] Yes (Please label this PR as **<code>release-notes</code>** and 
complete the section on Release Notes)
   ## Release Notes
   If you have tagged this as either backward-incompat or release-notes,
   you MUST add text here that you would like to see appear in release notes of 
the
   next release.
   
   If you have a series of commits adding or enabling a feature, then
   add this section only in final commit that marks the feature completed.
   Refer to earlier release notes to see examples of text
   
   ## Documentation
   If you have introduced a new feature or configuration, please add it to the 
documentation as well.
   See 
https://docs.pinot.apache.org/developers/developers-and-contributors/update-document
   


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

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



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to