[SERVER-12855] createIndexes 'numIndexesAfter' field missing if there are errors Created: 24/Feb/14 Updated: 14/Jun/19 Resolved: 14/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kamran K. | Assignee: | Zach Yam (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||
| Sprint: | Execution Team 2019-06-17 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The 'numIndexesAfter' field is missing from the createIndexes result document when an index build fails – even if a previous index build succeeded within the same command. This could be confusing to users who might expect that no indexes were created because there's a 'numIndexesBefore' field but no 'numIndexesAfter' field. Example result document:
Version: d0135ad0ed90118ad2015283f22b0219c0df3301 |
| Comments |
| Comment by Zach Yam (Inactive) [ 14/Jun/19 ] | |
|
When this command fails, it does not report numIndexesAfter because no indexes would have been built.
This command has changed such that both indexes are built at the same time. If one of them fails, then both of them fail | |
| Comment by Zach Yam (Inactive) [ 14/Jun/19 ] | |
|
This is what the output looks like:
| |
| Comment by Dianna Hohensee (Inactive) [ 29/May/19 ] | |
|
We should determine whether this behavior still exists or was modified in the last 5 years. | |
| Comment by Daniel Pasette (Inactive) [ 02/Mar/14 ] | |
|
Also noticed that numIndexesBefore isn't returned in some cases, which could be fixed by setting it earlier. |