Choosing Between Term and Match Queries in Elasticsearch
Learn when to use 'term' vs 'match' queries in Elasticsearch to avoid the common problem of missing documents caused by field analysis mismatches.
Loading…
ReadMeFeed / Community knowledge
#full-text-search
Real questions. Useful conversations. Find the people who know your stack.
elasticsearchCouchbase FTS and N1QL: A Practical Pattern for Search-First Apps
Use Couchbase Full-Text Search to shortlist document IDs by relevance, then fetch full documents with N1QL. A practical pattern for search-first applications that avoids expensive bucket scans.
couchbaseUsing Couchbase Full‑Text Search: Create, Query, and Avoid Common Pitfalls
Learn how to set up a Couchbase Full‑Text Search (FTS) index, run queries from Java, and what to watch out for—analyzers, index health, and numeric fields.
Fine‑Tuning Full‑Text Search in SourceEngine: BM25, Indexing, and Common Pitfalls
Learn how to enable SourceEngine’s full‑text search, tune the BM25 ranking algorithm, and avoid typical mistakes. Includes a concrete schema, query example, pagination advice, and verification steps.
sourceengineOptimizing Text Search in Neo4j: Choosing the Right Full-Text Index Strategy
Stop using slow CONTAINS queries in Neo4j. Learn how to implement full-text indexes, choose the right analyzer for your language, and validate search relevance using Lucene scoring.
Speeding up IMAP search with Dovecot’s Lucene‑based full‑text search
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.
dovecotNeo4j Full-Text Search: When to Use Native Indexes Over External Engines
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.
neo4jChoosing Between Couchbase FTS and Elasticsearch for Application Search
When deciding how to implement search for a Couchbase‑backed application, you can either use Couchbase Server’s built‑in Full‑Text Search or hook up an external Elasticsearch cluster. This guide compares the two options, discusses trade‑offs, and walks through a sample validation test.
Neo4j Text Search: Native Full-Text Index vs. Elasticsearch Integration
A decision guide for choosing between Neo4j's native Lucene-based indexes and Elasticsearch integration based on latency, consistency, and scale.