-
-
Notifications
You must be signed in to change notification settings - Fork 612
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 for term alternatives in phrase. #2281
Comments
We support the sql like You may also have a look at quickwit, which is built on tantivy for log search. |
That use case and syntax seems rather niche, so I'm not sure we would want to add that in the query parser. maybe @fulmicoton has an opinion on this |
Not a targetted solution, but wouldn't a |
This use-case is one of the main reasons why Elastic Search Span API exists :) Maybe I oversimplified the example, but analytical queries (e.g. incident detection) can consist of dozens of terms/alternatives.
Personally, I'm not sure about this as well (because of complexity for generic user). But it would be great to have ability to encode this information through some IR (like Elastic did with Span API). Also I need to mention, that parsing is not the main problem with this issue: if we expand non-trivial phrase into alternative of trivial, we'll have
Hello, @adamreichold! Yes, it works. |
So if I understand correctly, you would want a |
@npatsakula is it for quickwit or tantivy? |
@fulmicoton, the ideal option would be to support the ES Span API in the quickwit, but it quite tricky and requires a lot of work (e.g. slop evaluation for non-trivial sub-queries). I assumed (maybe, by mistake) that change of that size and complexity would be unwanted in the quickwit mainstream, so I published smaller issue for tantivy. |
Hello! First of all, I want to thank you for your awesome work on tantivy, it's great!
Motivation
I'm trying to use
quickwit
/tantivy
for non-structured log search and stuck with migration from Sphinx/Manticore.Using
Sphinx
query syntax I can write something like:But with
tantivy
I need to expand this expression by hand:If I have more than two elements (in alternative or in phrase), then writing and reading the query becomes more difficult:(
Solution
It would be great to have some syntactic sugar or rust low-level API (I can parse query by myself) to avoid such boilerplate. Also I would enjoy to implement this feature by myself, but I will need some help around query evaluation.
The text was updated successfully, but these errors were encountered: