[SERVER-76258] Flag when time-series granularity isn't modified after collection creation Created: 18/Apr/23 Updated: 29/Oct/23 Resolved: 03/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Michael Gargiulo | Assignee: | Arun Banala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||
| Sprint: | QI 2023-06-26, QI 2023-07-10 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
With the addition of fixed-interval bucketing in PM-2724 we can add Query optimizations for rewrites (PM-3324) when a fixed-interval granularity is used and not modified. However, we currently don't have a way to flag to Query that all buckets have the same fixed granularity since they can be changed by users via collMod to inform when rewrites are applicable/safe. We could add a flag to the collection on creation that says "these parameters have not been modified" and just unset it if we change them. |
| Comments |
| Comment by Githook User [ 03/Jul/23 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: |
| Comment by Githook User [ 30/Jun/23 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: |