Category: Search
FHIR Data Model with Couchbase N1QL
Couchbase is a JSON database that has now become an alternative to the traditional RDBMS. It has achieved this, not only by providing the industry-leading Key-Value store and the same query and ACID translation capabilities that organizations have come to...
FTS and N1QL: Better MongoDB in Operator Performance Querying Multiple Arrays
Introduction Couchbase Full Text Search (FTS) is a great fit for indexing multiple arrays and executing queries with multiple filter predicates in arrays. In this article, I’ll demonstrate the advantages of using FTS over GSI (Global Secondary Index) for array...
Announcing Couchbase Server 6.5 GA – What’s New and Improved
We are pleased to announce the release of Couchbase Server 6.5 GA with stellar features that lead the innovation in the NoSQL database market. We are excited to once again pioneer some of the most sought-after relational capabilities in the...
Introducing Geo Bounded Polygon Query in Full Text Search
Geo Bounded Polygon Query The ability to perform text search with geospatial query capabilities is a very powerful and effective feature from full text search(FTS). And we are bringing the more flexible geo bounded polygon query feature to FTS in...
Full Text Search Indexing Best Practices by Use Case
Introduction Full text search (FTS) indexing can be challenging for those who are not familiar with search in general. In this post, we’ll take some common search use cases and work through the creation of appropriate indexes following best practices...
Introducing FTS with N1QL
Topics this article will cover What’s good with N1QL? What about FTS? But why FTS within N1QL? Basic N1QL+FTS queries Deploying N1QL+FTS Syntax(es) Abilities & limitations N1QL+FTS Internals Covered-index vs Non-covered-index queries More N1QL+FTS query examples What’s next? 1. Couchbase’s...
Few Index Management Tips – FTS Best Practices Part II
We have already seen a handful of best practices for defining an FTS index in part1, now let’s explore a few useful tips about the operational and maintenance aspects of an index. A user who is new to the...
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...