15 June 2020 Release Notes¶
Version 1.1.170
Feature Highlights¶
Order Run Details Page Redesigned¶
As part of an ongoing infrastructure update to the DataKitchen platform, the Order Run Details page has received a makeover!
The page has a new layout that consolidates access to most data in a toolbar. Other improvements also address usability.
- Reduced scrolling required to access and view results
- Quick access to logs
- New feature to display runtime variables
- New feature to browse node-specific run data
- Auto-redirect to the new order run when resuming a stopped or failed order run
The following images preview the new features. See Order Run Details for more information. [DEV-3030]
Order Run Details Default View¶

Order Run Details Toolbar¶

Node Details Sidebar¶

Other Fixes & Enhancements¶
Test String Evaluation Updated to Recognize Intended Boolean Values: A user discovered that the system failed to parse a Boolean test metric that was expressed as a string. When the test returned either "True" or "False" as a string, the system always evaluated the results as a Boolean "True" and failed tests that should actually pass. This issue has been resolved with a code update to parse any true/false strings as Boolean values so that "False" never equals "True." [DEV-6289]
System Adds Default Port for SFTP Connection: Users reported that container nodes failed to connect to SFTP schemas unless they designated a port number. This issue has been resolved with additional code checks to ensure that the default port 22 is injected when users specify no value. [DEV-6096]
Logged Resource Usage Metrics Updated: In an effort to address a defect and increase the accuracy of the metrics, DataKitchen has changed its methods of collecting and reporting resource usage in order run logs. Previously, the disk space usage reported in the logs included any space required for shared infrastructure, in addition to the actual disk space used for processing. This release introduces a more accurate measure of disk space that accounts for only the process usage. See Runtime Resources for more information. [DEV-6138]
Order Runs Stop on Errors: Recently, failed order runs remained active in the system, preventing users from submitting new runs of an order. Logs indicated memory resource issues because the original order runs were not terminating properly. This issue has been resolved with additional cleanup following any errors. [DEV-6515]