[SERVER-35717] fassert rawSize of TypeBits is greater than 0 Created: 21/Jun/18 Updated: 27/Oct/23 Resolved: 22/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Storage NYC 2018-07-02 | ||||
| Participants: | |||||
| Description |
|
If the first byte of the type bits is 0x80, in 4.2 it will mean we have type bits longer than the 127 bytes constraint. We should change this dassert to fassert in 4.0 so that users will know they are reading the incompatible key string. |
| Comments |
| Comment by Xiangyu Yao (Inactive) [ 22/Jun/18 ] |
|
We actually decided to let 4.0.x support reading long TypeBits so it should not fassertĀ for that case. Closing this. |