Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.6.2, 6.6.3, 7.0.0, 7.0.1
-
Triaged
-
1
-
No
Description
Starting with version 6.6.2, the Feed Boundary is a persistent setting in the Function’s definition and can only be set or altered when a Function is created, undeployed or paused.
The tool couchbase-cli should no longer require or support the "--boundary" option.
Create a Eventing function working function "m1" with at least one document in the source bucket.
Use the couchbase-cli tool to deploy it
couchbase-cli eventing-function-setup -c localhost -u Administrator -p password --deploy --name m1 --boundary from-now
|
SUCCESS: Request to deploy the function was accepted
|
The --boundary from-now is ignored as in 6.6.2+ and 7.X the feed boundary is part of the function definition and NOT selectable at deploy time.
Use the couchbase-cli tool should now say:
SUCCESS: Request to deploy the function was accepted, but the option --boundary was ignored due to depreciation as the Function itself defines the preferred feed boundary.
|
Also if we drop the option --boundary the Function should still deploy but it doesn't in 6.6.2+ and 7.X
couchbase-cli eventing-function-setup -c localhost -u Administrator -p password --deploy --name m1
|
ERROR: --boundary is needed to deploy a function
|
The --boundary option is deprecated and should not be required