[SERVER-69264] Fail time-series index builds due to mixed schema only at commit time Created: 31/Aug/22 Updated: 29/Oct/23 Resolved: 05/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Gregory Noma |
| 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: | Execution Team 2022-10-03, Execution Team 2022-10-17 | ||||||||
| Participants: | |||||||||
| Description |
|
We return an error on the primary if we detect mixed schema data in a document. See code.
This can cause CannotCreateIndex to escape from the index build which is not allowed. |
| Comments |
| Comment by Githook User [ 05/Oct/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |
| Comment by Gregory Noma [ 04/Oct/22 ] |
|
This isn't actually a bug due to this check at commit time. I've updated the ticket accordingly. |
| Comment by Louis Williams [ 31/Aug/22 ] |
|
I noticed this bug because I saw the addition of CannotCreateIndex to this assertion. We shouldn't be adding any error codes to that list, because in almost all cases, this indicates a potential bug like the one I described. |