You can test that an undeployed or paused Eventing Function can get this setting, but I don't know how to read it from the DCP/KV side.
First create an Eventign Function MYFUNC in the UI then try to read "dcp_window_size" it will be "null" or non existent.
curl -X GET -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' | jq .dcp_window_size
|
|
null
|
The default is added internally if it is never added to the function MYFUNC 20*1024*1024 or 20971520. Now set it to something smaller say 80*1000 or 80000 this is 80K bytes.
curl -X POST -d '{"deployment_status":false,"processing_status":false,"dcp_window_size":80000}' -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings'
|
Now verify the Function definition has the setting we expect 80K or "80000".
curl -X GET -s 'http://'${CB_USERNAME}:${CB_PASSWORD}'@localhost:8096/api/v1/functions/MYFUNC/settings' | jq
|
.dcp_window_size
|
|
80000
|
Ritam Sharma and Jeelan Poola this dial DCP_WINDOW even if we eventually change it CC.next to a smaller value wouldn't have detrimental impacts as Dave Rigby points out