[SERVER-23619] Allow the delimiter set recognized by text search tokenizer to be configurable Created: 08/Apr/16  Updated: 27/Dec/23

Status: Backlog
Project: Core Server
Component/s: Text Search
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Kelsey Schubert Assignee: Backlog - Query Integration
Resolution: Unresolved Votes: 5
Labels: qi-text-search
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-22583 Allow text search to OR exact phrases Backlog
related to SERVER-23599 text index unique constraint violation Closed
Assigned Teams:
Query Integration
Participants:

 Description   

This feature would enable users to include or exclude delimiter characters. For example, the user could specify whether to treat "twenty-three" as one word or two words by including or excluding the "-" character from the set of delimiters.



 Comments   
Comment by Aurelius Wendelken [ 16/Dec/19 ]

Hey is there any plan to implement this in the near future? Having problems with https://purplepee.co search causing wired results when queering for 'abra-card-abra.com' the hyphen or other delimiter are the problem... Would really love to help you out, but I'm not famiar with C++...

Comment by Ruben Inoto [ 17/Jan/18 ]

+1 - This would be really helpful in our case

Generated at Thu Feb 08 04:03:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.