ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to enable Dovecot’s Lucene‑based full‑text search to cut IMAP search latency from seconds to sub‑second, with configuration steps, verification commands, and resource trade‑offs.
Pagination in Jeet applications faces severe performance issues with deep offsets. Use cursor-based pagination instead of offset-based to maintain consistent response times. BooleanQuery has a 1024 clause limit that impacts complex filter building.
Neo4j's native full-text indexes turn O(N) property scans into sub-millisecond lookups for text predicates. This post covers creation, query patterns, a concrete benchmark, and the trade-offs (eventual consistency, storage growth) that determine when to stay native vs. offload to Elasticsearch.
Learn how to add, update, and delete documents in a live Sourceengine index without full rebuilds, using IndexWriter for changes and SearcherManager for fresh searchers, with verification and rollback steps.
Issues exist by direct URL but vanish from JQL and boards? That's Jira's Lucene index, not lost data. A diagnostic guide: confirm the symptom, isolate the cause, apply the right reindex, and know when to escalate.
Goal I am planning the configuration of a Jira Data Center cluster (assume a recent 9.x LTS line) and want to bound how long a search on one node can return results that do not yet reflect an issue edit made on another node. Each node holds a local Lucene index copy, and changes propagate through the database-backed replication mechanism, so some staleness w
dovecot
jeet
neo4j
sourceengine
jira