TopGit
GitHub Repo Review

Elasticsearch: what users say about paging and durability

elastic/elasticsearch
ETopGit review image for elastic/elasticsearch
Review by Topgit.dev for elastic/elasticsearch, with GitHub repository stats and README context.
Quick verdict

Elasticsearch runs as Elastic's distributed engine for search and analytics, indexing JSON documents over REST APIs and returning near real-time results across large datasets. The README frames it as covering full-text search, vector search, and log or metrics data in one system rather than several. Reach for it if you need all three under one roof; skip it if a single database index already covers your search volume.

Stars
★ 78.5k
Forks
⑂ 26.2k
Language
Java
License
See repository
Topic
Data
Updated
Nov 2026
Homepage
GitHub

Paging through aggregation results was a wall for one early Elasticsearch user. On the project tracker, @aaneja, 2014-01-27 reported that "Terms aggregation does not support a way to page through the buckets returned" and had been trying to limit buckets with a min doc count setting plus an exclude filter for buckets already seen. That thread drew 207 comments and 134 reactions before it closed. The excerpt does not say how it ended.

Elasticsearch is a Java search engine that the README now pitches as a distributed search and analytics engine, a scalable data store and a vector database, with RAG, logs, metrics and APM among its listed uses.

The numbers give the setting. The project dates from 2010-02-08 and has 78,668 stars. Forks sit at 26,252, and the tracker holds 6,560 open issues, which is the backdrop for any single complaint. The latest push in the bundle is dated 2026-11-12, so the code keeps moving even though every opinion below is older.

A second worry is about durability. On Hacker News, @eclark, 2015-05-05 read the source and concluded that "ES is considering a write to be durable if it is put into a userspace buffer", adding that data reaches the kernel when the buffer fills and is synced on a timer. That is one reader's interpretation of the code as it stood in 2015, and I have no later comment in the bundle that confirms or corrects it.

The praise is broad rather than specific. Also on Hacker News, @reilly3000, 2021-08-09 said Elastic has competition in parts, "but as a whole package it stands alone", and that its "speed and versatility definitely differentiate it from other similar systems", noting it can act as a log aggregator, a search engine and a personalization system. @thedougd, 2021-08-08 offers the most practical account: they used to be "a huge proponent of Elastic.co for search", paid for the Elastic Cloud Enterprise product to run an internally hosted Elastic as a service, and ran a proof of concept on the open source stack before asking for money for commercial support. The excerpt cuts off before saying what changed their view.

The evidence is thin. That is four opinions from four people, three of them on Hacker News and one in a GitHub issue, with the newest dated 2021-08-09. Nothing from 2026 comments on the current release.

Before adopting it, check how a write is acknowledged in the exact version you plan to run, and try your own aggregation paging pattern there. Both reports are old enough that a quick test against your data is the safer check.

View on GitHub ↗

Related repositories

Source & attribution

Facts and quotes sourced from the elastic/elasticsearch GitHub repository and its README.

GitHub data · last synced Nov 12, 2026Reviewed by Henry
← Back to TopGit

Curious whether elasticsearch is right for you?

Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about elasticsearch.

GitHub