Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions modules/ROOT/pages/_partials/_page-index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,10 @@ endif::xref--pfx-sgw[]
:server-eventing-constructs--xref: {svr--xref}{server-eventing-constructs--page}[Couchbase Eventing Language Constructs]
:server-eventing-constructs-crc64--xref: {svr--xref}{server-eventing-constructs--page}#crc64_call[Eventing -- crc64()]

:server-eventing-terminologies--page: eventing:eventing-Terminologies.adoc
:server-eventing-terminologies--xref: {svr--xref}{server-eventing-terminologies--page}[Eventing Terminology]
:server-eventing-terminologies--xref-bindings: {svr--xref}{server-eventing-terminologies--page}#section_mzd_l1p_m2b[Bucket Bindings]

:server-collections--page: learn:data/scopes-and-collections.adoc
:server-collections--xref: {svr--xref-7x0}{server-collections--page}[Couchbase Collections]
:server-collections-default--xref: {svr--xref-7x0}{server-collections--page}#default-scope-and-collection[Default Collections]
Expand Down
4 changes: 2 additions & 2 deletions modules/ROOT/pages/server-compatibility-eventing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,9 @@ Here we provide details on how {server-eventing--xref} relates to data changes i

== Using Eventing

You can use Eventing and Sync Gateway connected to the same bucket, when Eventing operates in *read only* mode.
You can use Eventing and Sync Gateway connected to the same bucket, when Eventing operates on server buckets in *read only* mode -- see {server-eventing-terminologies--xref-bindings} for how to do this.

To do this, you must write your Eventing function to be *idempotent*; to behave correctly when the same mutation is seen more than once.
You should write your Eventing function to be *idempotent*; to behave correctly when the same mutation is seen more than once.
This is necessary because:

* When a single document update is made directly by Sync Gateway, such as those replicated from Couchbase Lite, it generates a single server mutation that writes both the document body and the metadata.
Expand Down