api: Missing search result despite record being available in Elasticsearch
Describe the bug
On searching for “Bengaluru” on Geocode.earth, we see the result Bangalore, KA, India as the topmost result.
However, a self-hosted full planet build does not return the record in search results, despite being imported in Elasticsearch.
Steps to Reproduce
- Search for “Bengaluru” on the Pelias compare tool
- There are two results, with first one being
Bangalore, KA, India - Searching in the self-hosted build does not include the above place in the results. a. Out of the two results in Geocode.earth results, only the second result is returned in the self-hosted version.
Expected behavior The search results in self-hosted installation and Geocode.earth should be identical, since the record can be found in Elasticsearch.
Environment (please complete the following information):
OS: Linux (Ubuntu 20)
Additional context We are running a full planet Pelias build in a VM using the Docker setup.
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 19 (5 by maintainers)
By administrative regions I mean things like cities/regions/countries, these populated places form the place hierarchy such that a address/street/venue is parented by one or more administrative regions.
From what I can see from what you’ve posted the API is returning only administrative records when elasticsearch is disabled, these are provided by the placeholder docker container.
You’ll notice that the results differ depending on whether elasticsearch is online or not, when online a query such as
Berliner Straße 86, Potsdam, BB, Germanywill return address records, but when it’s offline you’ll only get results for the region, in this case it’s returning Potsdam.This isn’t a ‘cache’ per-se since the results are different depending on which backend services are online.