Category: Full-Text Search
Running FTS Queries in N1QL
We already discussed how the Like % clause is potentially harmful for your application at scale, and why you should consider using Couchbase Full-Text Search instead. One thing we haven’t mentioned yet is why you might prefer Couchbase FTS over any...
Customer 360 – Part 4 – Analyzing Your Data
OK, so we’ve looked at building aspects of a Customer 360 solution in previous posts. We looked at an overview of what’s involved in part 1, and since you’re reading this, I’m assuming that the threat of having to think...
Build autocomplete or typeAhead using Full Text Search
What is Autocomplete vs Type Ahead? Autocomplete as the wikipedia says “Autocomplete, or word completion, is a feature in which an application predicts the rest of a word a user is typing” It is also known as Suggestions or Type...
FTS Performance Improvements in 6.5.0 – Part 2
For all those who are restlessly eager, let me reveal the deep dark secret of all the performance optimisations in FTS in 6.5.0 is, “ Do less And Do it less often ** ” And I am sure you would...
A Glimpse of FTS Performance Improvements in 6.5.0 – Part 1
Ever since the nimbler, refined scorch indexing format released in Couchbase 6.0.0, the FTS team has been pretty excited about the future optimisation potential unlocked with the newer indexing scheme. With the 6.5.0 release, we have essentially embarked on a...
Scorch Index Type – Why does it matter?
Index types in Full Text Search (FTS) – refers to the collective specification of the inverted index format and it’s storage aspects. Scorch is the advanced and evolving index type. But before delving further into the details of scorch, its...
Approaches to Query Optimization in NoSQL
A man returned home after walking around the globe for eleven years. Next day, when he told his wife he’s going to the corner store, she asked him: “are you taking the short route or the long one?”. Queries can...
Search & Rescue: 7 Reasons N1QL Developers Use Search
People don’t want a four key index. They need a four-ms response. Ted Levitt Application development is demanding. Each application is trying to progress on behalf of the customer — searching for the right product or the right form, ordering,...
Searching JSON: compare text search in Couchbase and MongoDB.
“Apps without search is like Google homepage without the search bar.” It’s hard to design an app without a good search. These days, it’s also hard to find a database without a built-in search. MySQL to NoSQL, Sybase to Couchbase,...
N1QL & SEARCH: Leverage Full-Text Search (FTS) Index in N1QL
With Couchbase v6.5, Full-Text Search is now integrated into the Couchbase N1QL query construct. Customers can now leverage FTS indexes directly with N1QL. This provides developers a single API to combine N1QL exact predicate matching and FTS powerful searching. The...
Full-Text Search Indexing Best Practices & Tips – Part 1
Full-Text Search – Indexing Tips Understanding the Full-Text Search (FTS) indexing options are essential for building the right index for the job at hand. The right index here refers to a lean and rich enough inverted index that can serve...
Announcing Couchbase Server 6.0 with Analytics
We are proud to announce that Couchbase Server 6.0 is now available, with the central theme of helping reduce the time to insight from enterprise applications. As part of this release, Couchbase Analytics service is now officially available. After two...
English