3 ms·
Oh man, https://github.com/elastic/elasticsearch-py/issues/1734 https://github.com/elastic/elasticsearch-py/issues/1734 is a disappointing read. I know ES wants
by rio517 5y ago
Oh man, https://github.com/elastic/elasticsearch-py/issues/1734 https://github.com/elastic/elasticsearch-py/issues/1734 is a disappointing read. I know ES wants to save their business, but alienating users isn't exactly the path to success.
- deleted 5y ago[deleted]
- vosper 5y agoFWIW, the ES team implemented a change that I requested via GitHub, and I’m just some guy who’s not even a paying customer. The change involved the behavior of force merge, and probably didn’t affect too many people. It’ll allow my employer (and hopefully some other companies) to make more efficient use of our disk space. I’m really appreciative of the way they considered and then implemented my request.
- rio517 5y agoThat's good to hear.
- waste_monk 5y agoI know someone who works at Elastic and it sounds like a really nice workplace (in terms of culture, average competency level across all employees, etc.), and that seems to be reflected in their products.
- gertrunde 5y agoI'm not sure I regard that particular example as actually bad. The response of "use the client version that matches the server version" seems perfectly fair.
- alkz 5y agoelastic 5.x is ANCIENT and no one in their right mind should still use that for any production workload
- deleted 5y ago[deleted]