[SERVER-76300] Remove CollationMatchesDefault::kNoDefault enum state Created: 19/Apr/23 Updated: 29/Oct/23 Resolved: 07/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Arun Banala | Assignee: | Hima Sheth (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QI 2023-06-12 |
| Participants: |
| Description |
|
There is currently no logic based on the enum state CollationMatchesDefault::kNoDefault. It looks like the state was added in anticipation for future use. The CollationMatchesDefault enum is only used in time-series code and the CollationMatchesDefault::kNoDefault is supposed to be used for collection-less aggregation. We should just get rid of this state in order to simplify the logic around collators. |
| Comments |
| Comment by Githook User [ 07/Jun/23 ] |
|
Author: {'name': 'hima sheth', 'email': '55309402+himasheth@users.noreply.github.com', 'username': 'himasheth'}Message: |