[SERVER-9352] Log entire index specification Created: 15/Apr/13 Updated: 27/Oct/15 Resolved: 28/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Stephen Lee | Assignee: | Phillip Quiza |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, the logs will indicate if an index is built on a collection. This event includes output on the index field specification and whether the background option is used, but other important options, like unique, dropDups, and sparse, are missing. These (or maybe all) options would be useful in determining what the index options were historically vs. currently. |
| Comments |
| Comment by Matt Kangas [ 28/Aug/13 ] | ||
|
We changed a log message. Should we document this change? Example from the code review: Old message format:
New:
| ||
| Comment by auto [ 28/Aug/13 ] | ||
|
Author: {u'username': u'pilliq', u'name': u'Phillip Quiza', u'email': u'pquiza@gmail.com'}Message: Signed-off-by: Matt Kangas <matt.kangas@10gen.com> |