stoty commented on pull request #1210: URL: https://github.com/apache/phoenix/pull/1210#issuecomment-829461725
The motivation for the audit logger is to log all data modifications for compliance purposes. This is a colossal wast of storage and resources, but some users have this legal requirement. The goal of the original logging implementation is mostly to provide data for operational purposes and performance operations. For example, in query logging, we only log the parameters at trace levels, while in the audit log we always want to log them, as it's useless without this. We also don't want to to do statistical logging for audit, as it would defeat its purpose. We have serveral things to log (query, paramters, query plan, statistics, etc) At the extreme end, you could specify what to log for each query type, and specify the logging probability. (Possibly complicating this by filtering for tables or other objects) However, this would be quite a large and awkward matrix to configure. The current solution is a relatively simple point solution to add the audit logging capability. It does not preclude the possibility of adding a more full-featured and flexible logging implementation later. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
