Also it can cause performance problems if you have really heterogeneous data with lots of different fields https://www.elastic.co/guide/en/elasticsearch/reference/curr...
Also it can cause performance problems if you have really heterogeneous data with lots of different fields https://www.elastic.co/guide/en/elasticsearch/reference/curr...
Same with scaling, scaling ES is super easy until you realize your index sizes aren't playing nicely with sharding or something and have to start working around that.
Clickhole feels like it's targeting what most people end up using ES for. Comparing it to ES and talking about what's missing is kind of missing the point imo.
Otherwise elastic doesn't require much operational time, may be an hour a week.
You pretty much want to keep your indices around 50gb and the ILM works well to manage that.
“You gonna have a bad time”. You can automate a lot of stuff around elasticsearch, but when you provide/source it within company - other teams may not be as knowlegable and can shoot themselves into the foot very easly.
Ive seen it multiple times by now. People have no idea how to manage the size of their clusters.
But, most of the time, it "just works".
Hearing these argument about rigid schemas saving time tells me that nobody has had to support teams with 200+ apps.
^ This guy actually manages infra