Skip to content

8 September 2020 Release Notes

Version 1.1.182. Note that versions 1.1.180 and 1.1.181 were deployed to DataKitchen testing environments only.

Feature Highlights

Orders Page Refreshed in Web App

As the DataKitchen web app refresh project advances, the Orders page gets an update! The redesign consolidates the data displayed and adds new columns that list the user who created the order and the order's schedule status. [DEV-3028]

Tour the Orders page

()

  • Filters: Users can refine the order list based on recipe, variation, status, and order-creation time selections. Note that you can filter by Order Status, but that status is not actually displayed in the table.
  • Order Actions: Items in this drop-down list allow users to Delete All orders, Delete Completed orders, and Run Variation Once. The Run Variation Once option opens a dialog where users can select the variation to run.
  • Select All: Users can check individual orders or select all to display a Delete function.
  • Reload Data: This button refreshes the table if an order run ID has not yet displayed for an order. The system automatically polls an active order run for its status for the first 30 seconds of a run.
  • Search: Type a part or all of an order ID to find it in the list.
  • Recipe/Variation: Click one of these links to open the Order Metrics page for the variation.
  • Schedule status: For scheduled orders, this column shows the schedule status. For orders run manually, the status is N/A.
    • Active: Schedule is ready for the next run of the order.
    • Inactive: Schedule had a critical failure and cannot be used.
    • Stopped: Schedule was manually stopped by a user.
    • N/A: No schedule set for this order.
  • Order Run ID: Click one of these links to open the Order Run Details page. Orders with multiple order runs display the three most recent orders with a Show More button.
  • Order Run Status: This column shows the current status of the order run. Click the Reload Data button to update the status.
    • Active: Order run is executing.
    • Complete: Order run finished processing without errors.
    • Error: Order run failed.
    • Stopped: Order run was manually stopped by a user.
    • Resumed: Order run was resumed as a new order run.
  • Order Run Actions: Click the three-dot menu to Copy Order Run, Delete Order Run, or Resume Order Run (when an order is in an error or stopped state).
  • Stop button: Click this button on active schedules to stop the schedule from its next run.

Kitchen Merge Gets a Makeover

This release updates the web app process for merging kitchens by introducing a single page with quick access to conflicted files, a three-panel file diff tool, and simple conflict resolution controls. [DEV-3377]

See Merge Kitchens for more information.

Page Previews

()

View file changes and resolve conflicts in a three-panel view.

()

Open a sidebar with a summary of changes in the source kitchen.

()

More options offer faster navigation following successful merges.

Revert Kitchen Feature Now Available in Web App

Revert Kitchen enables users to rollback any kitchen to its previous state. It can revert kitchen merges—with or without merge conflict resolutions—or single updates. Previously released only as a command line option, this release introduces the function in the web app on the Kitchen History page. [DEV-6454]

See Revert Kitchens for more information.

()

The Revert kitchen link appears in the upper right corner of the Kitchen History page.

Use Revert Kitchen with Caution! Note that the Revert Kitchen feature to rollback previous updates and merges can be dangerous! The revert should be used only with extreme caution!

Agent Status Displays in Run Variation Dialog

A DataKitchen Agent allocates resources in memory and disk space for running recipe orders. An agent must be online and have sufficient resources for any order to run. The web app provides an Agent Status widget, accessed from the top menu bar, that informs users of its current state.

Now that same information is available when users click to run a variation or node! This release adds a section to the Run Variation and Run Node dialogs, so users can assess the resources for processing their orders. If an agent is offline or being checked for its status, the Run button is not active and the order cannot initiate. See Agents & Resources for more information. [DEV-6799]

()

Users can run a variation when the agent is online.

()

Users cannot run a variation when the agent is offline.

Other Fixes & Enhancements

Node Editor Updated with Additional File Settings: When a recipe node is configured with a SQL database source or sink to write to or read from a file, the system needs to know details on how to map the data to the file. This release adds multiple fields to the web app Node Editor for defining delimited text files, such as CSV files. Previously, users could specify only column and row delimiters for these files via the web app. See File Settings for SQL Connectors for more information. [DEV-6833]

()

Order Delays Resolved: Recently, users experienced delays in order runs starting or order runs getting stuck on ingredient nodes. The problems were effects of the system not releasing connections and not handling ingredient order run timeouts correctly. These issues have been resolved, and orders run with the expected performance. [DEV-6001, DEV-6687]

Order Validations Restricted to Relevant Content: When users submit orders, the system performs a series of validations to provide immediate notification of potential problems. The system prevents orders from running when it identifies missing secrets, missing variables or overrides, and missing or invalid node configurations. A defect in the system caused these pre-order validations to inspect recipe elements that were not required for an order, in addition to the content of the order submitted. This issue has been resolved, and pre-order validations are now limited to the scope of each order. [DEV-4885]

Order Run Details Graph Shows Proper Node Data: The Order Run Details page was presenting nodes that had not run yet as status "Unknown" and without the proper graphical data for all graph modes. This issue has been resolved, and these nodes are shown in "Not Run" node status with all of the relevant graphics in the Node Type, Node Components, and Number of Tests graph modes. [DEV-6522]

Variables Retain Single Quotes at Runtime: Users found that when defining variables that included single quotation mark characters as override values, the system stripped the quotes at runtime and caused nodes that used those variables to fail. This issue has been resolved, and variables with single quotes compile properly when defined at any level of the override hierarchy. [DEV-6788]

Container Icons Re-Sorted for Easier Selection: When adding or editing a container node, a user can select or upload different icons to represent the node in the graph. The All Icons tab of the Select an Icon dialog did not display both built-in and user-uploaded icons in a combined alphabetical list. This issue has been resolved, so that users have a single, alpha-ordered list on that tab. See Manage Container Icons for more information. [DEV-6795]

Child Kitchen Does Not Inherit Parent Description: Recently, when users created child kitchens without entering a kitchen description, those kitchens were inheriting the description of the parent kitchen. This issue has been resolved, and child kitchens can be created with blank description fields. [DEV-6782]

Trivial Error Hidden from Logs: Several users reported seeing several cryptic, trace-level entries in their order run logs: TRACE [Aug 21 13:20:51] Error getting resources for a4d582a6-e3d2-11ea-8df3-d219c1b9a152-cnhhl: 404 - {"message": "Not found"}. This message indicates that heavy traffic slowed the ability to retrieve information. It is neither a harmful situation nor a useful entry for user troubleshooting purposes. This issue has been resolved by preventing this type of message from writing to the logs. [DEV-6942]