Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
Mad Hatter
-
1
Description
The first of the eventing examples, which is on /eventing/eventing-example-data-enrichment.html, no longer tracks the UI. So some directions are unclear, and some UI options are not referenced. I've not looked at the other three examples, but they could probably benefit from a QE inspection of some kind. Here are my notes on the first example:
Step 1 should be clear as to whether the buckets can be Couchbase or Ephemeral. Since
the metadata bucket might be ejected, it should not be ephemeral, since ejection would
mean its destruction. As a Couchbase bucket, it should have no TTL: this needs to
be emphasised elsewhere, I suspect, in the Eventing docs; since TTL will destroy it
at some point.
The source and target buckets can be either Couchbase or Ephemeral.
Steps 2 and 3 need to be clearer in terms of how to add the document. On the row for
the source document, click the Documents tab, then click ADD DOCUMENT.
In the Procedure, for the Bindings option, explain that binding alias must be selected
from the drop down, 'tgt' specified as the 'alias name...', target selected from the drop
down as the bucket to write to, and 'read and write' selected as the mode. Then, need
to explain the other options.
Step 8. Confirm Deploy Function: explain the feed boundary, and the difference between
'Everything' and 'From now', and the exact meaning of the subtitle: Execute the new
function for all invocations henceforth.
Step 9. Clarify that the Documents tab to be clicked on is the one in the row for the
'target' bucket on the Buckets screen.
Step 10. Would be nicer actually to show the document within the Target bucket, so
the user can see what has been added.