[PR] Support intermediate request-scoped data in catalog generic table events [polaris]

["rishii-19-works (via GitHub)" <gi...@apache.org>]

rishii-19-works opened a new pull request, #3392:
URL: https://github.com/apache/polaris/pull/3392

   This PR adds support for attaching and propagating intermediate, request-scoped data across catalog generic table events.
   
   Following the approach proposed in #3391, the same event metadata instance is now reused between the corresponding before and after generic table events. This allows intermediate objects produced during request processing (for example, response payloads) to be shared with downstream event listeners without coupling listeners to API responses or re-deriving state.
   
   A focused test is included to verify that intermediate data attached during the before event is correctly available in the corresponding after event.
   
   This change addresses #3209 and keeps the scope intentionally minimal, limited to generic table load events, to establish a clear and extensible pattern for future event types.


-- 
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: issues-unsubscribe@polaris.apache.org

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

Re: [PR] Support intermediate request-scoped data in catalog generic table events [polaris]

["rishii-19-works (via GitHub)" <gi...@apache.org>]

rishii-19-works commented on PR #3392:
URL: https://github.com/apache/polaris/pull/3392#issuecomment-3728742774

   Hi, thanks for the earlier guidance.
   
   I’ve followed the approach suggested in #3391 to propagate intermediate request-scoped data across before/after generic table events.
   
   I’m currently running into CI compilation failures around how intermediate data should be attached (event wrapper vs metadata vs underlying PolarisEvent). I’ve tried a few variants, but it looks like I’m misunderstanding the intended API surface.
   
   Could you please advise which object is expected to own intermediate data in this flow (the service event wrapper, the metadata, or the underlying PolarisEvent), and how it should be propagated to the after-event?
   
   I’ll update the implementation accordingly. Thanks for your patience.


-- 
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: issues-unsubscribe@polaris.apache.org

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

Re: [PR] Support intermediate request-scoped data in catalog generic table events [polaris]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] closed pull request #3392: Support intermediate request-scoped data in catalog generic table events
URL: https://github.com/apache/polaris/pull/3392


-- 
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: issues-unsubscribe@polaris.apache.org

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

Re: [PR] Support intermediate request-scoped data in catalog generic table events [polaris]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #3392:
URL: https://github.com/apache/polaris/pull/3392#issuecomment-3868921312

   This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.


-- 
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: issues-unsubscribe@polaris.apache.org

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