[SERVER-60577] Add logic to check time-series buckets for mixed-schema data at index time Created: 08/Oct/21 Updated: 29/Oct/23 Resolved: 30/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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 2021-11-01, Execution Team 2021-11-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Users that upgrade from earlier versions of the server may contain mixed-schema data in their time-series buckets. As long as the catalog flag that indicates whether a time-series bucket may contain mixed-schema data is set to true, we need to validate all the buckets when trying to index time-series measurements. There are two possible outcomes:
|
| Comments |
| Comment by Githook User [ 30/Oct/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 30/Oct/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Dan Larkin-York [ 08/Oct/21 ] |
|
As a brief note, it looks like the right place to plug in and add this logic isĀ here, prior to filtering. That said, we'll have to check that every insert path funnels through here, and there isn't some earlier filtering step in some cases. |