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.

Sign up for GitHub

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

Jump to bottom

fix: Handle '.geoip_database' index when creating alias #24

Merged
merged 1 commit into from
Dec 14, 2021
Merged

fix: Handle '.geoip_database' index when creating alias #24

merged 1 commit into from
Dec 14, 2021

Commits on Dec 14, 2021

  1. fix: Handle '.geoip_database' index when creating alias 

    Newer versions of Elasticsearch natively include a GeoIP database.

The code to set up the convenient 'pelias' Elasticsearch index alias
gets tripped up by this, as it wasn't expecting any other indices to
exist besides the main Pelias index.

We don't want to require people to name their Pelias indices anything
specific (though they generally start with `pelias-` according to our
project conventions).

What we can do is filter out the '.geoip_database' index when creating
the alias. Then the first index seen will be a Pelias index.
    @orangejulius
    orangejulius committed Dec 14, 2021
    Configuration menu
    Copy the full SHA
    afca4dc View commit details
    Browse the repository at this point in the history