[I] Introduce reason codes in server http requests to controller [pinot]

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

mcvsubbu opened a new issue, #12055:
URL: https://github.com/apache/pinot/issues/12055

   pinot servers send HTTP requests to the controller for posting a completed realtime segment,  posting an indication that realtime segments have stopped consuming, or that the consumer could never be created.
   
   Currently there is a reason string that is included as an argument. This is error prone. A reason code makes it easier to incorporate code for appropriate action, given a particular reason.
   
   The con side of a reason code is that it is a bit harder to evolve. We need to be careful writing code on the controller side, since servers may send unknown reason codes. As long as we follow some careful practices, introducing reason codes should get us to a better place.
   


-- 
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@pinot.apache.org.apache.org

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


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