[SERVER-72279] Consider using row store fallback for enormous fields in CSI Created: 20/Dec/22 Updated: 24/Jan/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
For enormous fields (BinDatas, giant strings, etc) it may not make sense to include this in the column index. This could be avoided by storing a row store fallback marker instead of the field itself. The most primitive way to do this would be to have a tunable threshold for when to index a value vs when to use the row store marker. |
| Comments |
| Comment by Ian Boros [ 20/Dec/22 ] |
|
Intentionally not putting this in any milestone, as we don't plan on doing this for the project. |