adutra opened a new pull request, #2998:
URL: https://github.com/apache/polaris/pull/2998

   <!--
   ๐Ÿ“ Describe what changes you're proposing, especially breaking or user-facing 
changes. 
   ๐Ÿ“– See https://github.com/apache/polaris/blob/main/CONTRIBUTING.md for more.
   -->
   
   This PR implements the action items from the following discussion threads:
   
   - https://lists.apache.org/thread/yx7pkgczl6k7bt4k4yzqrrq9gn7gqk2p
   - https://lists.apache.org/thread/rl5cpcft16sn5n00mfkmx9ldn3gsqtfy
   - https://lists.apache.org/thread/5dpyo0nn2jbnjtkgv0rm1dz8mpt132j9
   
   Summary of changes:
   
   - Introduced a `PolarisEventType` enum holding the 150+ event types.
   - Introduced a `PolarisEventMetadata` interface as suggested by 
@adnanhemani, exposing: timestamp, realm ID, principal, request ID, and OTel 
context.
   - Introduced a `PolarisEventMetadataFactory` to centralize the logic for 
gathering the various elements of an event metadata.
   - Modified `PolarisEvent` to expose 3 new methods:
     - `UUID id()`
     - `PolarisEventType type()`
     - `PolarisEventMetadata metadata()`
   - Persistence of OTel context is done in `additional_properties` as 
suggested by @flyrain.
   - Added `InMemoryBufferEventListenerIntegrationTest` to verify that all 
contextual data is properly persisted.
   
   ## Checklist
   - [ ] ๐Ÿ›ก๏ธ Don't disclose security issues! (contact [email protected])
   - [ ] ๐Ÿ”— Clearly explained why the changes are needed, or linked related 
issues: Fixes #
   - [ ] ๐Ÿงช Added/updated tests with good coverage, or manually tested (and 
explained how)
   - [ ] ๐Ÿ’ก Added comments for complex logic
   - [ ] ๐Ÿงพ Updated `CHANGELOG.md` (if needed)
   - [ ] ๐Ÿ“š Updated documentation in `site/content/in-dev/unreleased` (if needed)
   


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