From e42c515a5fcc459644c75b177a2a49faf066c414 Mon Sep 17 00:00:00 2001 From: Renat Akhmerov Date: Wed, 18 Apr 2018 13:11:59 +0700 Subject: [PATCH] Release note for not persisting '__task_execution' in DB Change-Id: I55bdc141e0d8ca73df06aa8dfaec49e8798366f9 --- ...istent_data_from_task_context-c5281a5f5ae688f1.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 releasenotes/notes/remove_redundant_persistent_data_from_task_context-c5281a5f5ae688f1.yaml diff --git a/releasenotes/notes/remove_redundant_persistent_data_from_task_context-c5281a5f5ae688f1.yaml b/releasenotes/notes/remove_redundant_persistent_data_from_task_context-c5281a5f5ae688f1.yaml new file mode 100644 index 000000000..7970a36a5 --- /dev/null +++ b/releasenotes/notes/remove_redundant_persistent_data_from_task_context-c5281a5f5ae688f1.yaml @@ -0,0 +1,10 @@ +--- + +fixes: + - Mistral was storing some internal information in task execution + inbound context ('task_executions_v2.in_contex' DB field) to DB. + This information was needed only to correctly implement the YAQL + function task() without arguments. A fix was made to not store + this information in the persistent storage and rather include it + into a context view right before evaluating expressions where + needed. So it slightly optimizes spaces in DB.