3 ms·
Im working with a rather unusual setup, namely that we use Elasticsearch as our primary data store. This article struck something with me — the client libraries
by 9dev 3y ago
Im working with a rather unusual setup, namely that we use Elasticsearch as our primary data store. This article struck something with me — the client libraries provided by Elasticsearch are just so, so bad. Fragmented, badly to not documented, different in every language… it’s just a pain in the ass. Errors aren’t documented at all - for one of our client libraries, I actually had to poke the server until it spat out errors, so I could add code to parse the JSON returned. And I still don’t know if I got everything, or if that message property will be there with the next error.
Sometimes I think they expect you to read and parse the response JSON manually.
Oh, and did I mention the horrible docs yet? For some methods, there just isn’t anything. Or stuff like „getFoo - returns the foo“.
That shit is infuriating, I tell you. Going to jump ship the microsecond something better appears.