Michael Kirk

It somehow didn't occur to me that we could make the jump to elastic8 without jumping to the modern client. Great observation @missinglink. > I would like to hold off...

By way of an update, as of yesterday, the [`projects/north-america`](https://github.com/pelias/docker/compare/master...michaelkirk-pelias:docker:mkirk/elastic8#diff-dce0b417b7f4198ea25707e7140707912b9729e84a9fe9c5c6602c5d27f04019) integration tests running on es8 are at parity with the master branch. ``` Aggregate test results Pass: 233 Improvements: 18...

In case it wasn't clear, I have (I believe) a fully functioning pelias stack on top of elastic8. And I was hoping to feed those changes into the project in...

My own needs are pretty humble at this point. There's an annoying timeout bug (https://github.com/pelias/docker/issues/217#issuecomment-1310547892) that doesn't occur with elastic 8. Additionally, I wanted to dig into some performance issues...

Thanks for the feedback @missinglink. > dropping support for 6 so we can increase support for 8, ideally merging things in smaller manageable batches to avoid having to do it...

Hi @Alex-SHG - no big changes other than what's already been covered in this thread. I'm still hoping the people managing the project will review and merge https://github.com/pelias/config/pull/142, and then...

> Is it possible to predict approximately when the switch to 8 will be possible? I'm not a maintainer of this project - just a contributor, so I definitely couldn't...

By way of an update, I've been happily using pelias on es8 for maps.earth (www and iOS) for about 10 days. No issues so far. In fact I have seen...

Hah, I suppose p99 is a dumb metric when my buckets often have less than 100 points. Here's a new chart plotting __median__ response time (now in millis) and also...

I'm working on this as part of https://github.com/pelias/schema/pull/488, but I had some thoughts related strictly to this new npm-module, regardless of the "support es8 work" in #488. > @elastic/elasticsearch replaced...