-
Notifications
You must be signed in to change notification settings - Fork 4
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
Searching for two terms doesn't work as expected #63
Comments
@wires I need more details, cannot replicate |
when you pass something into q it is (should be?) interpreted as a lucene query string. IIRC this is only applied to |
Ok, reopened, tagged as enhancement. |
Possibly relevant, I had a similar issue some time ago when querying Elasticsearch via REST, it turned out that by indexing the option 'skip stopwords' was active, this makes that all stop words are filtered out ALSO from the queries since they cannot have any effect. |
Searching for Maarsmansteeg 19
and
give same results
would expect lucene query string to work "Maarsmansteeg AND 19"
The text was updated successfully, but these errors were encountered: