Products · Product
Elasticsearch
Raised as a usability problem by 55 people on Hacker News over 15 years (2012–2026), in 47 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Simple searches require confusing, complex JSON queriesUnreviewed
20122026- Elasticsearch's JSON query syntax is verbose and confusing to work with2022-10-24
- Building complex JSON queries for simple searches is confusing to the user2020-07-09
- JSON query DSL is hard to write; SQL-like queries like renaming fields are impossible without reindexing2018-03-21
Documentation is hard to use without knowing what to search forUnreviewed
20122026- Documentation is confusing when you don't already know what to look for2023-01-25
- Documentation is so poor that first-time users struggle to find their way2014-07-11
- Documentation reads like marketing brochure, hard to find clear concise info2014-04-24
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Must manually refresh the index before written data can be read back2026-01-16
- Product names need many indexes and trial-and-error tuning to search well2025-07-23
- Field type conflicts at scale are common and annoying to deconflict2024-11-13
- Adding authentication to Elastic APIs and Kibana is so confusing it is nearly impossible without a managed service2024-08-30
- Website and docs are so vague that people can't tell what the service is2024-08-29
- Calls tables 'indexes' and fields 'mapping', confusing for users coming from databases2024-08-03
- Query language is hard for users to use2023-06-22
- Errors undocumented, so developers must probe the server to learn error formats2023-06-11
- Logs with conflicting JSON and plain-text types get silently dropped, with no setting to fallback2023-04-28
- Documentation is confusing when you don't already know what to look for2023-01-25
- Requires tuning and planning that is a dark art for new users2023-01-24
- Schema mismatches are hard to resolve and the search API is awkward to work with2022-11-07
- Too big and complicated to understand how ranking works2022-11-06
- Too much unrelated complexity makes it hard to figure out how to do simple full text search2022-11-06
- Elasticsearch's JSON query syntax is verbose and confusing to work with2022-10-24
- Maintaining, monitoring and scaling the cluster takes massive effort without a big team2022-08-08
- Hard to tell which part of a complex search caused results to be included or excluded2022-05-02
- Obscure error messages nobody can decipher, and hard to tune or understand2021-09-29
- Users must remember to index correctly and tune technical settings before logs are searchable2021-09-28
- Setting up authentication is a difficult, lengthy process compared to other databases2021-08-18
- Sending Ubuntu systemd logs to Elasticsearch requires an endless maze of choosing between components2021-08-09
- Slash character is special in queries, making logging searches painful and nearly unusable2021-04-12
- Building complex JSON queries for simple searches is confusing to the user2020-07-09
- Adding nodes often forces a reindex or reshard, and slowness is very hard to debug2020-03-25
- Subscription tiers and terminology are confusing, and the subscriptions page is hard to make clear2020-02-24
- Rejects log records whose fields have mixed types, returning 400 errors on ingest2020-01-04
- Newly added events don't appear in the search index, confusing users, and syncing is unreliable2019-10-23
- Easy to build something that seems to work but fails in production2019-09-16
- Elasticsearch is horrible to operate and is overkill for small non-cluster use2019-07-19
- Very hard to tune; RAM needs are unpredictable and OOMs are common2019-04-19
- Simple grouped average took five attempts over two days due to poor documentation2018-12-15
- Doing data analytics is very difficult and annoying with its custom query language2018-12-14
- JSON query DSL is hard to write; SQL-like queries like renaming fields are impossible without reindexing2018-03-21
- Leftover files from failed install cause obtuse error wasting lots of time2018-03-01
- No reference docs for mappings, endpoints or settings, so behaviour must be guessed by trying2018-03-01
- Hard to get running: inconsistent config formats, missing docs, breaking changes between versions2018-03-01
- Beginners waste time figuring out how to clear an index without losing its mapping2017-08-27
- Upgrades failed to accept data and bit the author in undocumented ways2017-02-14
- Query syntax is arcane and hard to build from the docs2017-02-14
- Lists and code blocks are misaligned, making the page hard to read2017-02-10
- Can't find advanced options like filters in the query interface2016-10-06
- Commenter finds Elasticsearch API and documentation less intuitive than Solr's2016-10-06
- Disabling indexing for bulk loads is fiddly to set up2015-10-28
- Automatic schema guessing creates bad mappings that can never be changed2015-10-28
- Simple queries require 20+ lines of unintuitive code2015-10-28
- Elasticsearch setup was problematic as configured by a contractor2015-10-22
- Query syntax is awkward and behaves unintuitively, making it much more complicated2015-07-20
- All-in-one search bar with suggestions works poorly for the user2015-07-05
- No way to kill long-running queries except restarting the server2015-07-05
- Hard to architect and operate correctly; needs deep expertise and constant care2015-05-02