andrew4699 commented on PR #458:
URL: https://github.com/apache/polaris/pull/458#issuecomment-2494384537

   > What's the use case for logging it at all, that cannot be done from an 
Iceberg client or curl?
   
   This is intended to be server-side so Polaris knows more about its callers.
   
   > I have no problem with the functionality but I think it probably should be 
part of an eventing api. We may want to keep the complete history of the table 
somewhere (possibly not in the Catalog itself)
   
   Yes I think that would be a useful API and [this 
change](https://github.com/apache/polaris/pull/433) could help the project move 
in that direction. In some sense these 2 changes can make the value proposition 
clearer by first providing low-friction access to this unstructured, 
self-reported data.


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