-
Notifications
You must be signed in to change notification settings - Fork 24
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
Multi term search #14
Comments
@jciolek Any thoughts on this? |
Apologies for the delay. Ok, so here's what seems to be happening. First of all the query string:
gets parsed by qs to Now, I think it is a very good use case, and I am going to make some subtle changes to support it. I am thinking of adding array support to On a separate note, regarding your particular data structure @Mattchewone, I am wondering if you wouldn't benefit from having |
@jciolek Thanks very much for looking in to this. I am new to Elasticsearch and understanding the mappings I am still trying to get to grips with. Would having Many thanks |
@Mattchewone Not a problem. So in your case, the query string would be:
Which translates to an Elasticsearch terms query in filter context:
You can also have a look at the queries fired by https://hacker-search.net/, which uses feathers-elasticsearch. Specifically I hope that helps. |
Right, so I have read your original issue again and I gather what I just said above is probably not exactly what you are after. I understand you want ALL of the values to be present, not just some. I am working on it. |
Closed via #16 |
Steps to reproduce
Trying to get results by using multi-$phrase search using this query:
I am wanting to find all items which have both rock and pop as tags
Here is the data structure in Elasticsearch:
Expected behavior
I would expect it to build query and find for both the $phrased terms.
Actual behavior
I get this error
[illegal_state_exception] Can't get text on a START_ARRAY at 1:49
System configuration
feathers@2.1.1
feathers-elasticsearch@0.2.2
The text was updated successfully, but these errors were encountered: