[
https://issues.apache.org/jira/browse/DERBY-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364635#comment-17364635
]
Trejkaz commented on DERBY-5007:
--------------------------------
This would be useful for us.
We'd like a way to intercept the logging so that we can redact parameters
passed into the logger for privacy reasons.
Currently we have some users who outright refuse to send logs because
confidential information is contained in there. (e.g. the path to a database
contains the name of the user whose home directory it resides in.)
Currently the only option we seem to have is to provide a Writer where we
somehow try to parse the text sent to the writer, to try and recognise which
parts of the output are parameters, so that we can redact only those.
> Implement an alternative error-logging mechanism using the java.util.logging
> idiom.
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5007
> URL: https://issues.apache.org/jira/browse/DERBY-5007
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Richard N. Hillegas
> Priority: Major
> Labels: derby_triage10_11
>
> The Driver.getParentLogger() method introduced by JDBC 4.1 gives
> applications a way to hook into the error-logging mechanism used by the
> database--provided that the database does its logging via a
> java.util.logging.Logger. It would be good to support this idiom in Derby
> alongside the existing home-grown error logger. If we implement this support,
> then we can remove the extra dummy driver classes added by the
> derby-4869-24-ab-getParentLogger.diff patch as part of DERBY-4869. Those
> classes exist only to support the vacuous implementations of
> Driver.getParentLogger() which raise unimplemented-feature exceptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
