[SERVER-50991] audit createIndex on empty collection Created: 17/Sep/20 Updated: 29/Oct/23 Resolved: 18/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sara Golemon | Assignee: | Shreyas Kalyan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2021-02-22 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Comments |
| Comment by Githook User [ 18/Feb/21 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |
| Comment by Githook User [ 18/Feb/21 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |
| Comment by Eric Milkie [ 12/Feb/21 ] |
|
I wouldn't spend extra effort to change the natural behavior, which sounds like it will be "audit the _id index when it is automatically created with a new collection". I think I prefer that behavior as well. |
| Comment by Shreyas Kalyan [ 11/Feb/21 ] |
|
milkie This is a good question. I think it is a non-trivial amount of work to not audit the _id index that is created. I think it is not a bad thing to audit the _id field as well; the only potential downside I could think of is extra spam on the audit log. Is this a strong enough reason / is there a stronger reason to not include the _id field? Or were you advocating for the _id field to be audited? |
| Comment by Eric Milkie [ 03/Feb/21 ] |
|
Will this include auditing the _id index that is automatically created when a collection is created? |