26 May 2020 Release Notes

Version 1.1.167

Feature Highlights

Change to When Graph Nodes are Processed

Traditionally, the DataKitchen platform processes graph nodes level by level. For simple graphs, this order of operations works fine. In parallel graphs, however, processing level-by-level means that one "path" of the graph has to wait until another path catches up in node levels before it can complete its execution.

This release offers a change the order of execution to achieve more efficient throughput in recipe workflows. The platform can now process a node as soon as its predecessor completes its execution.

Note

New Graph Processing Available: The new sequential graph processing for fast throughput is turned off by default but can be turned on by request.

See Processing Graphs and, specifically, the Order of Execution section for more information. [DEV-6154]

Nodes do not process until all nodes in the previous level are complete.

If node_d required significant time to process, the level-by-level method suspended processing on node_e until node_d completed. This sequence delayed the entire order run.

A node begins processing when the previous node in the same path completes.

With the new sequential method, node_e and node_g can be processed while node_d is still in progress.

Other Fixes & Enhancements

Exported Graphs Show Container Node Icons: A recent feature release enabled users to select from default or custom icons when they added new container nodes to a recipe graph. When a user exported a graph, those icons were not displaying properly in the PNG image. This issue has been resolved, and graph exports display all container nodes as expected. [DEV-6234]

Secrets Page Displays Correct Inheritance: Recently, some users found that after they created a child kitchen and specified that the vault should be inherited from the parent kitchen, they received multiple vault entry errors when running a recipe. And, the Secrets page displayed the error: "No vault service configured for kitchen." In these scenarios, the configuration for the parent kitchen's vault was set to be NOT inheritable, but the UI indicated the opposite. This issue occurred infrequently but has been resolved by updating the UI to display the proper inheritance settings for kitchen vaults in the Configure Kitchen Vault dialog. [DEV-5943]

Containers Stop with Order Run Stop: Container nodes that run monitoring scripts with wait loops as well as new containers created during an order run were not stopping their execution when a user stopped the order run. Users discovered that these containers were still processing when they re-ran the recipe variation and saw duplicate events. This issue has been resolved with a change to force stop those containers. [DEV-6152]