[
https://issues.apache.org/jira/browse/CALCITE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371122#comment-15371122
]
Julian Hyde edited comment on CALCITE-1311 at 7/11/16 4:45 PM:
---------------------------------------------------------------
It would very nice to have this, but is it scope creep? If the backend server
already has auditing it wouldn't want Avatica doing it at another level.
Are we talking about data auditing here (e.g. if there is a batch insert of 100
rows, write those 100 rows out somewhere)?
How does this capability compare with metrics? Events such as "connection
created", "statement canceled" are similar to those that would be gathered by
metrics. So, would auditing and metrics write to the same place, and would they
use the same mechanism?
was (Author: julianhyde):
It would very nice to have this, but is it scope creep? If the backend server
already has auditing it wouldn't want Avatica doing it at another level.
> Add high-level record of interactions with the avatica server
> -------------------------------------------------------------
>
> Key: CALCITE-1311
> URL: https://issues.apache.org/jira/browse/CALCITE-1311
> Project: Calcite
> Issue Type: New Feature
> Components: avatica
> Reporter: Josh Elser
>
> It would be nice to have the ability to configure the Avatica server to
> create what is equivalent to an "audit log".
> This functionality would provide administrators the ability to inspect what
> queries were run and the user (client address and optionally the Kerberos
> identity).
> It would be nice to implement this as a framework and provide an initial
> "sink" binding which just writes to a file. This would let us push these logs
> to other systems automatically which would be nice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
