-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support wildcard in non-suffix position #5306
support wildcard in non-suffix position #5306
Comments
quickwit went up in ranking for our use case even with some rough corners here and there, evaluation was going great... Until we just to hit the wall with this showstopper. I wish it would be available right now, but alas. Fellas, any estimate on when this would be available, so we can reevaluate it? |
@tandr would love to discuss that with you, you can ping me (fmassot) on our discord server. |
Discord does not allow me to use sneakemail.com address (even that I am paying for it), so 🤷 |
This feature is crucial, and we hope to gain some traction and support for it. Bump |
I'm using the latest edge release as of 11 hours ago.. Is there a quick explanation of how to use this? I can't seem to get a wildcard inside a search string to work |
Does this support queries like |
it does, though you should avoid doing that, as it is probably the most expensive kind of query you can run right now. The index we use does pruning based on if the start of a token can match the provided query, which you can't do in that case |
Unfortunately, these are the type of queries that we are using a lot :(
|
that's interesting, |
Thank you for looking into that. But, I don't think I can ask users to "please insert |
omg... that was quick. Not that I understand the fix in tantivy fully, but thank you! Hopefully it will be merged soon, and dependencies will be updated, so I can continue with testing. |
currently we allow
field:value*
, but notfield:val*ue
The text was updated successfully, but these errors were encountered: