From 2c9312239fa014495c58fdffeba0a03683b24139 Mon Sep 17 00:00:00 2001 From: Jon Strabala <54073900+jon-strabala@users.noreply.github.com> Date: Tue, 5 Dec 2023 11:59:59 -0800 Subject: [PATCH 1/2] missing 7.2.0 language compatibility setting --- modules/eventing/pages/eventing-Terminologies.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/eventing/pages/eventing-Terminologies.adoc b/modules/eventing/pages/eventing-Terminologies.adoc index 87975f9cf2..5384a40885 100644 --- a/modules/eventing/pages/eventing-Terminologies.adoc +++ b/modules/eventing/pages/eventing-Terminologies.adoc @@ -167,7 +167,7 @@ The minimum value is 1 (the default) and the recommended maximum is 64. In most * *Language compatibility*: The language version of the Eventing Function for backward compatibility. + -If the semantics of a language construct change in any given release the “Language compatibility” setting will ensure an older Eventing Function will continue to see the runtime behavior that existed at the time it was authored, until such behavior is deprecated and removed. Note 6.0.0, 6.5.0, and 6.6.2 are the only currently defined versions and for newly authored Functions the default is the highest compatibility version available, currently 6.6.2. +If the semantics of a language construct change in any given release the “Language compatibility” setting will ensure an older Eventing Function will continue to see the runtime behavior that existed at the time it was authored, until such behavior is deprecated and removed. Note 6.0.0, 6.5.0, 6.6.2, and 7.2.0 are the only currently defined versions and for newly authored Functions the default is the highest compatibility version available, currently 7.2.0. + For example, accessing non-existent items from a keyspace returns undefined in 6.5.0, while in 6.0.0 an exception is thrown. In addition, only a Function with “language compatibility” of 6.6.2 in its settings will pass binary documents to the OnUpdate(doc,meta) handler. In addition, values of 6.0.0 and 6.5.0 will filter all binary documents out of the DCP mutation stream, only 6.6.2 will pass binary documents to the Eventing Function handlers. From 5b5015fec0f6639643e1eda29a9a6eca18684135 Mon Sep 17 00:00:00 2001 From: Jon Strabala <54073900+jon-strabala@users.noreply.github.com> Date: Fri, 15 Dec 2023 11:41:37 -0800 Subject: [PATCH 2/2] Update modules/eventing/pages/eventing-Terminologies.adoc Co-authored-by: sarahlwelton <110928505+sarahlwelton@users.noreply.github.com> --- modules/eventing/pages/eventing-Terminologies.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/modules/eventing/pages/eventing-Terminologies.adoc b/modules/eventing/pages/eventing-Terminologies.adoc index 5384a40885..3c4645574a 100644 --- a/modules/eventing/pages/eventing-Terminologies.adoc +++ b/modules/eventing/pages/eventing-Terminologies.adoc @@ -167,7 +167,9 @@ The minimum value is 1 (the default) and the recommended maximum is 64. In most * *Language compatibility*: The language version of the Eventing Function for backward compatibility. + -If the semantics of a language construct change in any given release the “Language compatibility” setting will ensure an older Eventing Function will continue to see the runtime behavior that existed at the time it was authored, until such behavior is deprecated and removed. Note 6.0.0, 6.5.0, 6.6.2, and 7.2.0 are the only currently defined versions and for newly authored Functions the default is the highest compatibility version available, currently 7.2.0. +If the semantics of a language construct change in any given release, use the *Language compatibility* setting to ensure continued compatibility for Eventing Functions authored using an older version, until the runtime behavior is deprecated and removed. + +Currently, version 6.0.0, 6.5.0, 6.6.2, and 7.2.0 are available. New Eventing Functions will use the highest available version. + For example, accessing non-existent items from a keyspace returns undefined in 6.5.0, while in 6.0.0 an exception is thrown. In addition, only a Function with “language compatibility” of 6.6.2 in its settings will pass binary documents to the OnUpdate(doc,meta) handler. In addition, values of 6.0.0 and 6.5.0 will filter all binary documents out of the DCP mutation stream, only 6.6.2 will pass binary documents to the Eventing Function handlers.