Skip to content
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

Open
wires opened this issue Aug 19, 2015 · 4 comments
Open

Searching for two terms doesn't work as expected #63

wires opened this issue Aug 19, 2015 · 4 comments

Comments

@wires
Copy link
Contributor

wires commented Aug 19, 2015

Searching for Maarsmansteeg 19

https://api.histograph.io/search?name=Maarsmansteeg&dataset=leidse-panden-1879

and

https://api.histograph.io/search?name=Maarsmansteeg%2019&dataset=leidse-panden-1879

give same results

would expect lucene query string to work "Maarsmansteeg AND 19"

@bertspaan
Copy link
Member

@wires I need more details, cannot replicate

@wires
Copy link
Contributor Author

wires commented Nov 2, 2015

when you pass something into q it is (should be?) interpreted as a lucene query string. IIRC this is only applied to name property. Better would be if we can pass in q=name:foo AND other:bar

@bertspaan bertspaan reopened this Nov 2, 2015
@bertspaan bertspaan added enhancement and removed bug labels Nov 2, 2015
@bertspaan
Copy link
Member

Ok, reopened, tagged as enhancement.

@sbocconi
Copy link

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.

@wires wires removed their assignment Nov 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants