From 253fd978c551a0e55c78f16d2cc2e0103982941f Mon Sep 17 00:00:00 2001 From: Renat Akhmerov Date: Wed, 19 Feb 2020 16:12:33 +0700 Subject: [PATCH] Release note for "convert_output_data" config option Change-Id: I99d30434c9d337529edae041427de05ffcf2ffd6 Closes-Bug: #1863857 --- ...output_data_config_option-4a0fa926a736de7e.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 releasenotes/notes/add_yaql_conver_output_data_config_option-4a0fa926a736de7e.yaml diff --git a/releasenotes/notes/add_yaql_conver_output_data_config_option-4a0fa926a736de7e.yaml b/releasenotes/notes/add_yaql_conver_output_data_config_option-4a0fa926a736de7e.yaml new file mode 100644 index 000000000..3cceed871 --- /dev/null +++ b/releasenotes/notes/add_yaql_conver_output_data_config_option-4a0fa926a736de7e.yaml @@ -0,0 +1,14 @@ +--- + +fixes: + - | + Added the configuration option "convert_output_data" in the "yaql" group. + This option, if set to False, allows to disable YAQL expression result + conversion. This fixes performance issues for lots of use cases where + a result of an expression is a big data structure. In fact, YAQL created + a copy of this data structure every time before giving it to Mistral. + This option can't be set to False when the corresponding + "convert_input_data" is True. Otherwise, it doesn't work correctly. + By default, the value of "convert_output_data" is True which keeps + backwards compatibility. +