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

0 results for Vista Center #357

Closed
missinglink opened this issue Nov 2, 2015 · 3 comments
Closed

0 results for Vista Center #357

missinglink opened this issue Nov 2, 2015 · 3 comments

Comments

@missinglink
Copy link
Member

I'm really not sure what is going on here... it appears to be a regression in master

http://pelias.github.io/compare/#/v1/search%3Ftext=vista%20center

POST /pelias/_search
{
   "query": {
      "match": {
         "name.default": {
            "analyzer": "peliasTwoEdgeGram",
            "query": "vista center"
         }
      }
   }
}

   "hits": {
      "total": 0,
POST /pelias/_search
{
   "query": {
      "match": {
         "phrase.default": {
            "analyzer": "peliasPhrase",
            "query": "vista center"
         }
      }
   }
}

   "hits": {
      "total": 510487,

/v1/place?api_key=search-xxxxxx&ids=qs:neighbourhood:23898:::usa:vista_center

@riordan
Copy link
Contributor

riordan commented Nov 2, 2015

I'll further complicate the matter; it does the same for autocomplete:

http://pelias.github.io/compare/#/v1/autocomplete%3Ftext=vista%20center

@missinglink
Copy link
Member Author

it turns out they are both stop words and so after those tokens are stripped the query becomes 'vista center' -> '', the same is true for avenue street and other places made entirely of stop words.

@riordan
Copy link
Contributor

riordan commented Jan 12, 2016

Diagnosed more fully in Issue w/ Stopwords for Autocomplete pelias/pelias#211

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

2 participants