[SERVER-19962] unicode::String needs a UTF-16 constructor Created: 14/Aug/15 Updated: 06/Dec/22 Resolved: 26/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Text Search |
| Affects Version/s: | 3.1.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adam Chelminski (Inactive) | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Operating System: | ALL |
| Participants: |
| Description |
|
RLP's performance is currently hampered by the fact that in diacritic insensitive search, tokens from RLP are converted from UTF-16 to UTF-8 to UTF-32 to UTF-8. By adding a UTF-16 constructor to unicode::String, this can be simplified to UTF-16 to UTF-32 to UTF-8. |
| Comments |
| Comment by Charlie Swanson [ 26/Oct/18 ] |
|
This seems like a performance improvement request for RLP, which we no longer use. Closing. |