You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WL#16214 Export Query Results to Object Storage (Part 3/12)
Bug#37069723 - WL16214 OPTIMIZER_TRACE shows query text with PAR ID
Bug#37035000 - WL#16214: PAR leaked in show processlist during export data
Bug#37069770 - WL16214 SELECT EXPORT using PAR ID seen in slow_query_log
Bug#37069714 - WL16214 General Log shows PAR id with SELECT EXPORT
Bug#37041886 - WL#16214: PAR leaked to audit log
AIM
=============
Ensure SQL queries containing sensitive information like PAR IDs
are safely logged without exposing sensitive data (specifically the PAR ID).
If the query requires exporting of query result to object storage,
then any pattern matching the /p/<parID>/n/ is replaced with
/p/<redacted>/n/
Moreover, we should refer to the rewritten query instead of the user
supplied one in such cases.
Change-Id: I4bb5f07fa3c7b9cf83a9ef6ba9e42154e75a44cb
0 commit comments