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


   ## Description
   
   #6576 Emit metric for upsert table metadata (store mapping from primaryKey 
to RecordLocation) memory usage in bytes.
   
   [Previous 
work](https://github.com/apache/incubator-pinot/pull/6204/files#diff-2fc79d140ad00f4fe862b03a12674c564a3cd85bc59e5397cb706a51a19faa39R46
 ) emitting metric for PK numbers.
   
   
   ## Upgrade Notes
   Does this PR prevent a zero down-time upgrade? (Assume upgrade order: 
Controller, Broker, Server, Minion)
   No.
   
   Does this PR fix a zero-downtime upgrade introduced earlier?
   No.
   
   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
   No.
   
   ## 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.
   
   this is a backward compatible change. 
   
   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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to