suneet-s opened a new pull request, #13760:
URL: https://github.com/apache/druid/pull/13760

   ### Description
   
   When submitting an ingestion spec, users may pass a map of metadata in the 
ingestion spec config that will be added to ingestion metrics.
   
   This will make it possible for operators to tag metrics with other metadata 
that doesn't necessarily line up with the existing tags like taskId.
   
   Druid clusters that ingest these metrics can take advantage of the nested 
data columns feature to process this additional metadata.
   
   #### Release note
   
   New: You can now add additional metadata to the ingestion metrics emitted 
from the Druid cluster.
   
   
   
   This PR has:
   
   - [ ] been self-reviewed.
      - [ ] using the [concurrency 
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
 (Remove this item if the PR doesn't have any relation to concurrency.)
   - [ ] added documentation for new or modified features or behaviors.
   - [x] a release note entry in the PR description.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [x] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [ ] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] added integration tests.
   - [x] been tested in a test Druid cluster.
   


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