Not long after, Elasticsearch made changes to how they version their products, and the next release skipped over versions three and four and went directly to
Along with this change in policy came an accelerated release schedule from Elasticsearch as their product offering and head-count grew, in anticipation of their IPO in mid-2018.
At this time, we were primarily focused on providing free geocoding APIs through Mapzen Search. Released in 2015, this was a significant shift for us as the open-source project had now evolved into a hosted API which grew in popularity through 2016 and 2017 as other organizations began integrating with Mapzen.
With this change came some maturity in how we handled releases; a hosted service can’t have any downtime. We learned a lot about continuous delivery, how best to do it in a live user-facing environment and most importantly how to handle major upgrades to dependencies, such as Elasticsearch, with zero downtime.
And then the unthinkable happened. Mapzen shut down. In January 2018 the teams split up and went different directions and with that went all the free hosted services. The future of Pelias and other Mapzen projects was unclear.
During this difficult time, we received a huge amount of encouragement and support from our community and it was clear that Pelias development must continue. What wasn’t clear, however, was exactly how the project would be funded in order to ensure continuity.
In early 2018 Geocode Earth was formed as an independent organization, wholly owned by the core developers and without external funding. Not a startup, but a small independent business focused on the sustainable development of Pelias.
During 2018 and 2019, we completely overhauled both the development process and the deployment process to use Docker containers, making Pelias easier than ever to deploy and develop. We also introduced new features such as improved support for alternative names of places, our open source free-form address parser and numerous performance and quality improvements.
In early 2019 we moved away from the
2.4 series which had served us well during the early stages of the project and shifted focus to the
5.6.x series. Lucene 6 came with a new datastructure for geo-point fields called Block K-D trees which reduced latency for all
With the end of a decade, came an upgrade to Elasticsearch 6.8.5, a much-anticipated release which came with a lot of performance improvements and a ~50% reduction of the on-disk index size.
We’re pleased to announce that Pelias is now compatible with the latest
7.5.x versions of Elasticsearch and with this update we say goodbye 👋 to version
Docker images are available right now on Dockerhub, you can find the corresponding configuration files on Github.
Photo credit: Memory Lane by Paul Yoakum.