[SERVER-11427] Audit logging for action 'renameCollection' needs to match the spec Created: 28/Oct/13  Updated: 11/Jul/16  Resolved: 29/Oct/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.4

Type: Bug Priority: Critical - P2
Reporter: bard.bloom@10gen.com Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

The spec says that bson-formatted data has format

{source: <old-ns>, target: <new-ns>}

But the data actually uses different keys:

{original: <old-ns>, new: <new-ns>}

----------------------------------------

Also, the renameCollection operation can fail if dropTarget is not true and the target collection already exists. No audit logging occurs in this case. It's not clear if any is necessary, since nothing happened, but other audit operations produce audit records in the case of failure so this one might.



 Comments   
Comment by auto [ 29/Oct/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-11427 update renameCollection's auditLogging to match spec
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/fd0dc99ed7c1996a3f2e94b7301936f63db63482

Comment by bard.bloom@10gen.com [ 28/Oct/13 ]

Sorry, I misread some tricky test output. Logging is done, but does not match the spec in all cases.

Generated at Thu Feb 08 03:25:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.