Have you ever created an application where you needed to save a document into Couchbase and then immediately query for that created document? It happens to me all the time when I’m developing. Take, for example, adding new data into a list where each list item is a new document. In many scenarios, you’ll want to update the UI that renders the list immediately after adding to it. The problem here is that the document you had just created may not show up in query results. This is because Couchbase indexers may not have processed the latest mutations against the Couchbase Bucket.
We’re going to see how to define our own scan consistency within a Node.js application that will yield variable results in our Couchbase N1QL queries.
No comments:
Post a Comment