rishii-19-works commented on issue #3209: URL: https://github.com/apache/polaris/issues/3209#issuecomment-3635989053
Hi @adnanhemani thanks for opening this issue. The use-case really makes sense I’m interested in contributing here, so I wanted to clarify a few things before I start working on anything From what I understood, the main idea is to make some intermediate data (like `LoadTableResponse` during a transaction commit) available to the event emitter even when it’s not actually part of the API response. I just had a couple of questions so I move in the right direction:- 1. Would you prefer using some kind of per-request context to store this metadata, or is there already any internal pattern in Polaris to pass such info between layers? 2. Are there any architectural constraints regarding Quarkus internals vs Polaris/Iceberg logic that I should keep in mind? 3. For the first PR, should I only focus on adding the mechanism for storing/passing this intermediate data, or also update a specific flow to show how it would work? Once I get your guidance on the approach I can start drafting something or work on an initial implementation Thanks! -- 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]
