DataKitchen DataOps Documention

Product Releases

Release notes for user-facing fixes and enhancements in the DataKitchen DataOps platform

28 September 2020, version 1.1.185

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • Filters and Pagination Fixed in Order Run Logs: When a user viewed order run logs while the order run was still processing, the Logs dialog generated an error generated on refresh. Following the error the log filters did not work and only the first page of log entries would display despite attempts to view other pages. This issue has been resolved with a refactor of the log store, and the Order Run Logs dialog functions as expected. [DEV-7063]
  • Kitchen Wizard Settings Persist: As a result of a recent database change, any updates on the Configure Kitchen page for the master kitchen caused the removal of existing settings for the Create Kitchen wizard. A second problem prevented rollback ingredients from displaying in the Delete Kitchen process. These issues were resolved with a hotfix, and kitchen configurations and wizards work properly. [DEV-7061, DEV-7067]
  • Order Metrics Updated for Numeric Test Results: Recently, the charts on the Order Metrics page were showing the results of all log tests, all tests with a variable used as the metric, and all tests against historic values (previous runs) as pass/fail, rather than plotting numeric test values in line graphs. This issue has been resolved with an update to the charting logic. The charts plot numeric test results as expected. [DEV-7018]

21 September 2020, version 1.1.184

FEATURE HIGHLIGHTS

Updates Make It Easier to Review and Troubleshoot Order Runs

User feedback on the new Order Run Details page prompted some enhancements in the display of order run and node data to reduce scrolling and facilitate review.

  • The Tests and Compiled Files sections of the Node Details sidebar can expand and collapse for ease in accessing all sections.
  • The Logs section of the Node Details sidebar has a link to open an Order Run Logs dialog pre-filtered for the node, rather than listing log entries within the narrow sidebar.
  • The Order Run Logs dialog has a search field in addition to the existing filters. Note that the log search only searches the Messages fields and is case sensitive at this release.
  • The logs include a new Warning log level. The Exception log level has been removed.
  • Log entries are numbered as displayed. When users apply filters, the line numbers may change.
  • The URL for an open Order Run Logs dialog contains user selections for filters and pagination, so users can share specific log sections more easily.
  • Log entries that have an associated exception stack trace can be expanded by Admin users only to reveal the trace details.

See previews below, and see Order Run Details for more information. [DEV-6759, DEV-6754]

The Node Details sidebar now has expandable sections and a link to pre-filtered logs.

The Node Details sidebar now has expandable sections and a link to pre-filtered logs.

Enhancements of the Order Run Logs dialog make log reviews easier.

Enhancements of the Order Run Logs dialog make log reviews easier.

Other Fixes and Enhancements

  • Variables Lists Include Kitchen Overrides: The web app offers a V drop-down list for quick variable entry in many fields. Some instances of this drop-down list did not include the kitchen override variables along with the system variables, base recipe variables, and variation override variables. This issue has been resolved; the V menus in the Edit Variable Set, Add Variable Set, and Edit Recipe Order Run Alerts dialogs now offer the complete list of available variables. [DEV-6556]
  • Kitchen Merge Warns of New Changes: If there are updates in a parent or child kitchen outside of but during a kitchen merge process, the merge preview becomes out of date. An enhancement in this release introduces a message warning the user to review the merge again. [DEV-6984]
  • Error Fixed in Promote Order Run Dialog: The merge kitchen process offers an optional step to copy order run information to the target kitchen. The Promote Order Run dialog was generating an error, "expression has changed after it was checked," on long text strings that were truncated in the interface. This issue has been resolved, and long strings no longer trigger an error. [DEV-7011]
  • Ingredient Node Allows Multiple Updates: When making changes to the configuration of an ingredient node, users found that the initial change was successful but the Update button was inactive for successive changes. This issue has been resolved, and the Update button is available for all modifications. [DEV-6941]

14 September 2020, version 1.1.183

FEATURE HIGHLIGHTS

DataKitchen Web App Posts User Notifications

This release introduces user notifications displayed on the Login page and accessible from the top toolbar of the web app interface. [DEV-6728]

Look in these locations for the following types of messages.

  • Planned system down time
  • User warnings
  • Product releases
  • Event announcements, such as webinars
  • Surveys
The new Login page displays public notifications.

The new Login page displays public notifications.

A new icon opens the Notifications list from the web app toolbar.

A new icon opens the Notifications list from the web app toolbar.

Platform Gains Order Run Alerts

An update to the Alerts feature introduces a test warning alert and refreshes the order run time exceeded alert. These alerts can be configured for an entire kitchen or at the recipe level, but each requires thresholds to be set in variations.

  • Warning alert: Node tests may be configured to take different actions on failures--stop execution, generate a warning, or log the incident. The new warning alert sends a notification to configured recipients when the number of test warnings meets the threshold set for the variation. The limit must be set for this alert to be sent.
  • Time Limit Exceeded alert: Users can set the maximum amount of time allowed for order run processing. This revised alert sends a notification to configured recipients if an order run meets the time threshold set for the variation. The limit must be set for this alert to be sent.

See Alerts for more information. [DEV-6698, DEV-6711, DEV-6746]

Configure the new alerts on the Configure Kitchen page (shown), during kitchen creation, or on the Recipes page.

Configure the new alerts on the Configure Kitchen page (shown), during kitchen creation, or on the Recipes page.

Set alert thresholds from variation actions on the Recipes page (shown) or from a tab on the Variation page.

Set alert thresholds from variation actions on the Recipes page (shown) or from a tab on the Variation page.

Other Fixes and Enhancements

  • JSON Decoding Updated for Control Chars: The system was generating JSON errors on control characters during order run execution. This issue has been resolved with an update to how the DataKitchen platform decodes JSON. Control characters such as '\t' (tab), '\n' (line feed), '\r' (carriage return), and '\0' (null) are now allowed inside JSON strings and will not throw errors. [DEV-6980]
  • Kitchen Overrides Added to Menus: The variables drop-down lists in three dialogs on the Recipes page now include variables configured as kitchen Overrides. The new variable set increases the lists in the Edit Recipe Order Run Alerts, the Add Variable Set, and the Edit Variable Set dialogs, which previously contained system variables, base recipe variables, and variation overrides. [DEV-6556]
  • Requirements Updated for Recipe Naming: This release includes new validations on recipe and variation names. Note these new restrictions and see Supported Naming Conventions for more information. [DEV-6928, DEV-6950]
    • Characters allowed: alphanumerics, underscore, dash
    • Syntax: must start and end with alphanumeric characters
    • Max characters: 63
  • Scroll Area Changed on Recipes Page: After the release of the redesigned Recipes page, users found the recipe tabs confusing when scrolling through multiple rows in the Variations table. The tabs appeared to align with the data as column headings. This issue has been resolved with an update to the scrolling behavior on the page. Now, the entire right pane scrolls up. [DEV-6595]
  • Delete Container Option Honors Default: Users found that the Delete Container feature for cleaning up runtime container resources used in node processing was not honoring its default "True" setting. This issue has been resolved, and runtime containers get removed post-processing when this option appears in a node's notebook.json parameters. See Delete Container Option for more information. [DEV-6993]
  • Browser Refresh Not Required with Revert: Following the recent release of the Kitchen Revert feature in the web app, users could not see the results of their reverts in the Recipes page or Node Editor without refreshing their browsers. This issue has been resolved, and the pages reflect the changes immediately. [DEV-6965]

8 September 2020, 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

  1. 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.
  2. 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.
  3. Select All: Users can check individual orders or select all to display a Delete function.
  4. 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.
  5. Search: Type a part or all of an order ID to find it in the list.
  6. Recipe/Variation: Click one of these links to open the Order Metrics page for the variation.
  7. 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.
  8. 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.
  9. 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.
  10. 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).
  11. 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.

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

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

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

More options offer faster navigation following successful merges.

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 Merges for more information.

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

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.

Users can access agent status information from the menu bar widget.

Users can access agent status information from the menu bar widget.

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 can run a variation when the agent is online.

Users cannot run a variation when the agent is offline.

Users cannot run a variation when the agent is offline.

Other Fixes and 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]

17 August 2020, version 1.1.179

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • Refresh Removed from Agent Status Function: The Agent Status function in the top, black menu bar has been modified in this release. The system no longer polls agents for resource data at 30-second intervals, and the Agent Online popup box no longer offers a refresh button. Instead, the system refreshes the resource data on demand at the time a user clicks the Agent Status icon to open the popup. [DEV-6808]

Agent Down Failures

The changes here result in Run Variation buttons being available at all times, even when an agent may not be ready to support an order run. While this scenario is rare, an order could fail with no useful feedback as to the cause. DataKitchen developers continue to work on agent-related features, and a coming release will address this gap, providing robust health checks and user messaging.

  • Orders Delete without Error: Recently, users found that when deleting an order via the web app, the system would display an error message. The order was deleted properly despite the error and was removed on page refresh. This issue has been resolved, and the delete function works as expected. [DEV-6794]
  • New System Variable Added: This release introduces the Agent system variable. This variable is compiled at runtime and resolves to the host name of the Kubernetes agent node where the recipe runs. It will be used in the future to increase agent visibility in logs and elsewhere in the platform. See System Variables for more information. [DEV-4092]

10 August 2020, version 1.1.178

Note that version 1.1.177 was deployed to DataKitchen testing environments only.

FEATURE HIGHLIGHTS

Node Status Indicators Redesigned in Order Run Details

The Order Run Details page depicts a graph as it is being processed. When the page displays in the Node Status graph mode, each node is shown in a color to indicate its processing status. This release includes enhanced status indicators using both colors and icons, as well as tooltips, to differentiate states and follow user accessibility guidelines.

See Processing Graphs and UI Order Run Details for more information. [DEV-6660]

Node status indicators include icons and tooltips. Note the legend in this image.

Node status indicators include icons and tooltips. Note the legend in this image.

Add Node Function Now Available in File Editor

A platform enhancement in this release provides File Editor users access to the Add Node module. Previously only available in the Nodes tab of the Recipes page and the Graph tab of the Variation page, this module now also opens as a dialog within the File Editor.

After adding a node, users must click the Update button to save the new node files. Note that users still have to connect newly added nodes in their graphs, either directly in the graph-setting-list object within the variations.json file, or by returning to the graphical view. [DEV-4716]

Users can now access the Add Node function from the File Editor.

Users can now access the Add Node function from the File Editor.

The Add Node dialog opens in the File Editor.

The Add Node dialog opens in the File Editor.

Other Fixes and Enhancements

  • New System Variable Added: This release introduces the {{WarningCount}} system variable. This variable can be compiled any time and resolves to the number of warnings logged during an order run. It will be used for a new alerting function but is also available for use in recipes via variable drop-down lists or via direct input. See System Variables for more information. [DEV-438]
  • Variation Metrics Display Properly: The previous release updated a library used on the Order Metrics page, and that update prevented the graphs from displaying. This issue was resolved immediately with a hotfix to correct the library. [DEV-6773]
  • SFTP Sink Validations Updated: While SFTP data sources require a key or wildcard attribute to designate files to load, SFTP data sinks can be referenced without configuring these elements. The system was generating an error incorrectly on valid SFTP sink configurations that did not include these elements. This issue has been resolved so that the keys or attributes are only required for STFP sources. [DEV-6614]
  • Order Metrics Page Error Resolved: When the Tests tab of the Order Metrics page included pass/fail test graphs, the platform generated a Javascript error for mishandling null values for colors. This issue has been resolved by setting the color to transparent. [DEV-6623]
  • Poll Interval Returned to Ingredient Node Config: User feedback to the newly released redesign of the Ingredient Node page revealed that the Poll Interval field was used more than originally thought. This field, which allows users to adjust the frequency that an ingredient node assesses the separate processing of an ingredient, has been added back to the Configuration tab. See Calling Ingredient Nodes From Nodes within Recipes for more information. [DEV-6760]

27 July 2020, version 1.1.176

FEATURE HIGHLIGHTS

Web App Refresh Simplifies Ingredient Node Page

The DataKitchen web app updates continue with a new design and simplified functionality on the Ingredient Node page. Ingredient nodes call pre-defined ingredient variations in order to execute a shared function or generate fresh output.

By removing several configuration fields and providing direct access to the underlying ingredient variation, DataKitchen designers and developers have offered an easier path for users to employ ingredients in their recipes.

Summary of Changes

  • Accessing and configuring the ingredient node in the Node Editor is now consistent with the other node types.
  • After selecting the underlying ingredient variation, the user sees a summary and graph of that variation, so it is clear what will be running in the ingredient node.
  • A link in the Node Editor opens the ingredient variation for editing in a new browser tab.
  • The node configuration reduces complexity by excluding some legacy fields:
    • ingredient failure options, as they are already set for the ingredient variation, and the ingredient node will fail on ingredient test failures
    • the agent group setting, as the ingredient will process using the agent defined for the ingredient variation's kitchen by default.
    • the polling intervals, as the node uses standard system polling.

See Calling Ingredients for more information. [DEV-4537, DEV-6675]

Page Previews

The Ingredient tab summarizes and links to the ingredient variation.

The Ingredient tab summarizes and links to the ingredient variation.

The Configuration tab simplifies node setup to timeout and variables settings.

The Configuration tab simplifies node setup to timeout and variables settings.

The Tests tab mirrors the standard test settings for other node types.

The Tests tab mirrors the standard test settings for other node types.

Other Fixes and Enhancements

  • Full Logs Displayed in Web App: Previously, the web app truncated the display and filtering of order run logs to the first 2000 lines. Users had to export larger logs to view all entries. This issue has been resolved with an enhancement to the Order Run Details page, so it now loads entire logs 200 lines at a time as users scroll down. And, filters apply to all log entries. The enhancement applies to the Order Run Logs dialog as well as the Logs section of the Node Details sidebar. See Logs for more information. [DEV-5420]
  • Merge Error Resolved for File Conflicts: The system generated errors during the kitchen merge process when child and parent kitchens had conflicts in specific categories of file extensions. Merge conflicts in .json, .txt, .md, and .sql files were not affected; but conflicts in other file types, such as .py, .html, .ipynb, or binary files, caused a merge to fail. This issue has been resolved converting the merged file content to bytes. [DEV-6736]
  • Data Source Adds to Container Properly: When a user created a container node without selecting a data source during the Add Node process, the platform was generating an error when the user later attempted to add the source in the Connections tab of the Node Editor. This issue has been resolved; container nodes update with the new data sources as expected. [DEV-6689]
  • Cron Expression Help Published: A new topic has been added to the DataKitchen platform documentation to help clarify the cron syntax supported by the order scheduler. This content includes information on time zone limitations. See Cron Expression Basics. [DEV-6683]

20 July 2020, version 1.1.175

FEATURE HIGHLIGHTS

Create Kitchen Wizard Redesigned

The latest web app update incorporates user feedback into the redesign of the Create Kitchen Wizard! The new process includes the following features.

  • Faster loading of the wizard and its steps
  • Forward and backward navigation among steps
  • A button to skip optional steps to expedite the child kitchen
  • A new Add Alerts step, as kitchen-level alerts are not inherited from the parent
  • All recipes from version control available for search and selection
  • Access to view problems with ingredient setup
  • A button to enter the new kitchen directly when the process is complete

See a preview of the new wizard below, and see Create a Kitchen for more information. [DEV-3038]

The Create Kitchen wizard now offers a step for alerts setup.

The Create Kitchen wizard now offers a step for alerts setup.

The redesigned wizard offers a search field for recipe selection.

The redesigned wizard offers a search field for recipe selection.

The Select Ingredients step provides more information on ingredient variations for the creation process.

The Select Ingredients step provides more information on ingredient variations for the creation process.

New Data Source & Sink Supported

The DataKitchen platform has added another new input/output connector that can serve as a data source and data sink. Now, users can configure their recipe nodes to connect to their Azure Data Lake Storage Gen2 (ADLS2) instances. [DEV-6264, DEV-6265]

DataKitchen introduces an Azure Data Lake Storage connector.

DataKitchen introduces an Azure Data Lake Storage connector.

Connection String Field Change

This field has been renamed with an underscore character for all Azure data sources and sinks.
connection-string
IS NOW
connection_string
Users with existing Azure Blob Storage recipes must update this property.

Other Fixes and Enhancements

  • Templates Updated for Recipe Files: The legacy description.json and variables.json recipe files contained pre-defined fields for configuring recipe-level order run alerts. With the release and increased use of the kitchen-level alert function, these fields became a liability for users who had to manually remove them to avoid runtime errors. This release introduces the simplified templates for these files. Description.json retains only the system default settings for alerts. [DEV-6411, DEV-6412]
{
    "description": "",
    "recipe-emails": {
        "recipe-over-duration-email-estimated-maximum-time-in-minutes": "240",
        "email-delivery-service": "aws-email"
    }
}
{
    "variable-list": {
        }
    }
}
  • Variation Edits Do Not Affect Order in Variation File: Users found that when they made changes to a variation using the Edit action in the Variations tab of the Recipes page, the updated variation moved to the bottom of the variation-list field in variations.json. This automatic sorting defect caused problems when users later attempted to resolve kitchen merge conflicts. This issue has been resolved with a patch to prevent any unintentional reordering of the variations.json file. [DEV-6625]
  • Order Scheduler Supports Literal Strings for Days: When configuring a schedule in the web app using the "On certain days of the week" option with a timezone entry, users found that order runs never execute at the expected times. This issue has been resolved with an update to the scheduler to fully support string literals for days of the week, such as MON,TUE,THU, with or without timezone definitions. See Schedule Syntax for more information. [DEV-6638]
  • Agents Settings Persist When Reloading Configure Kitchen Page: Users in kitchens that use custom agent groups discovered that their settings on the Configure Kitchen > Agents tab were not displayed in the web app following any refresh of the Configure Kitchen page. The issue was limited to the web app display of agent settings only. The defect occurred on manual browser refreshes, logins following session timeouts, as well as updates made elsewhere on the Configure Kitchen page. This issue has been resolved and the Agents tab only alters settings for user-initiated changes. [DEV-6630]

13 July 2020, version 1.1.174

FEATURE HIGHLIGHTS

New Data Source & Sink Supported

The DataKitchen platform has added another new input/output connector that can serve as a data source and data sink. Now, users can configure their recipe nodes to connect to their Teradata instances. [DEV-6260, DEV-6259]

DataKitchen introduces a Teradata connector.

DataKitchen introduces a Teradata connector.

Other Fixes and Enhancements

  • New Variables Appear in Web App: The newest system variables, {{ParentKitchen}} and ResumedOrderRunId now appear in variables drop-down lists in the web app interface. See System Variables for more information. [DEV-6628, DEV-6631]
  • Rollback Ingredients Shown in Delete Kitchen: The Delete Kitchen function was not displaying the rollback ingredient option without a page refresh. This issue has been resolved by replacing cached data with a new data request. [DEV-6474]
  • Kitchen Revert Function Tags Commits: An update to the new Kitchen Revert feature adds Git tags to each revert. Pre-revert and post-revert tags serve as failsafes in the event that a kitchen revert must be undone by DataKitchen Support. See Revert Merges for more information. [DEV-6609]
  • No Error for Empty String in Recipe Alerts: The new recipe template creates email-recipients fields in description.json, but the system was generating errors when any of those fields were left blank. This issue has been resolved with an update to field validations. [DEV-5691]

6 July 2020, version 1.1.173

FEATURE HIGHLIGHTS

New Commands Enable Kitchen Merge Rollbacks

This release introduces two new commands in the DataKitchen command line interface, DKCloudCommand. The kitchen-history and kitchen-revert commands are both associated with improvements to kitchen merge operations across the platform. Together, they provide a process for rolling back the results of a kitchen merge to prevent bad code from affecting production environments.

Similar to the Kitchen History page in the web app, the output of the kitchen-history (kh) command shows the record of kitchen updates, or Git commits, associated with a kitchen's Git branch. When users revert a kitchen merge, the history report is vital for confirming the outcome. See Kitchen History and Commands & Options for more information.

dk kitchen-history --help
Usage: dk kitchen-history [OPTIONS]

  Get Kitchen history

Options:
  -k, --kitchen TEXT   kitchen name
  -c, --count INTEGER  Number of commits to display
  --help               Show this message and exit.

The new kitchen-revert command and its shortcut kr enable users to rollback any kitchen to its previous state. It can revert kitchen merges—with or without merge conflict resolutions—or single updates. See Revert Merges and Commands & Options for more information. [DEV-6455]

dk kitchen-revert --help
Usage: dk kitchen-revert [OPTIONS]

  Revert latest kitchen commit (can be a merge or a simple commit)

Options:
  -k, --kitchen TEXT  kitchen name
  -y, --yes           Force yes
  --help              Show this message and exit.

Other Fixes and Enhancements

  • New System Variables Added: This release introduces two new system variables. These variables will not appear in variables drop-down lists in the web app until a future release, but users may manually write them in and use them via the command line interface. See System Variables for more information. [DEV-6387, DEV-6136]
    • {{ParentKitchen}} can be compiled any time and resolves to the name of the parent kitchen of the kitchen in which the variable is called.
    • ResumedOrderRunId is compiled at runtime of a resumed order and resolves to the order run ID of the original failed order run.
  • Report Issue Form Working: A recent update caused errors in the support request form accessed from the help icon in the web app. This issue has been resolved; the form works as expected. [DEV-6587]
The Report Issue form that opens from this menu is working properly.

The Report Issue form that opens from this menu is working properly.

  • Kitchen Names Can Start with Underscores: When users created kitchens named with initial underscore characters, they received errors when running orders. This issue has been resolved, and the platform allows the use of initial underscores in naming kitchens. [DEV-6301]
Kitchen names can begin with underscore characters.

Kitchen names can begin with underscore characters.

  • Step Validation Corrected for Action Nodes: When users added a step to an action node and selected "None" for the Result Type, they saw an error icon on the Steps tab and could not update the node. The system was incorrectly detecting the result type selection as invalid. This issue has been resolved by updating the validation rules. [DEV-6607]
  • Node Editor Recognizes No Updates: Under certain circumstances, users who opened a node in the Node Editor and then left the page without making changes encountered an Unsaved Changes dialog. This issue has been resolved with an update to the Node Editor. [DEV-6572]
  • System Executes Empty Script Files: Users who added a script file to a container node but left the script empty found that the node failed at runtime with a logged error, "No such file or directory." This issue has been resolved with an enhanced check for empty files that allows empty scripts to execute normally. [DEV-3374]

29 June 2020, version 1.1.172

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • New Kitchens Do Not Inherit Alerts: When users created child kitchens, the kitchen-level alerts set in the parent kitchens were copied. This behavior often resulted in alerts being sent to an unintended recipient list. This issue has been resolved by removing the inheritance of kitchen alerts. New child kitchens get created with an empty kitchen alert recipient list. See Configure Kitchen Alerts for more information. [DEV-6483]
  • Scheduler Handles Sunday Cron Option: Because Sunday can be expressed as a 0 (zero) or a 7 in a cron statement, the order scheduler was misinterpreting cron entries for some orders running on Sundays. This issue has been resolved with a code update to handle 0s and 7s in the same manner. For example, 0 20 * * 7 and 0 20 * * 0 both mean "at 20:00 on Sunday." See Schedule for more information. [DEV-6547]
  • Node Connections Allow At Signs: Users found that they could not enter the required username to connect to a Microsoft SQL Server, as the syntax @servername was not allowed by platform field validation. This issue has been resolved by adding the at sign (@) to the allowed characters in the username field for most database connections (DB2, MS SQL, MySQL, Oracle, Vertica, and PostgreSQL). [DEV-6248]
  • File Editor Saves Duplicate Keys: While building recipes using the File Editor, users can input invalid JSON, then view other files in the File Editor with or without saving the working file, and return to see all changes retained so they can continue building. This same scenario was not allowed if users copied keys within recipe files. Those keys were automatically removed when users viewed other files then returned. This issue has been resolved by updating the system to store duplicate keys while users view other files while remaining in the File Editor. The system, however, still prevents users from saving any file with duplicate keys. [DEV-6310]
  • Platform Warns Users of Invalid Changes: When users try to navigate away from a page with valid, unsaved edits, a warning dialog appears with cancel, discard, and save options. The platform did not provide a similar warning when users navigated away from a page with invalid changes. This issue has been resolved with a new warning dialog, offering cancel and discard options. The dialog appears on the Configure Kitchen, Variation, Node Editor, and File Editor pages. Additionally, the Update button now displays a tooltip on hover to explain why the button is not available. [DEV-5988]

22 June 2020, version 1.1.171

FEATURE HIGHLIGHTS

New Recipe Page Consolidates Configurations

The DataKitchen web app updates continue with a refresh of the Recipes page! The new design eliminates the Configure Recipe page, making most functions accessible on the Recipes page.

Users can now manage variations, nodes, graphs, variable sets (base variables and overrides), alerts, and schedules from a single page. See Recipes and Use the Recipes Page for more information. [DEV-4569]

Legacy recipe tools and settings appear on the new Recipes page.

Legacy recipe tools and settings appear on the new Recipes page.

Recipe Function Map
The following table can help users locate their favorite recipe functions in the new design.

Old Locations
New Locations

wrench icon (A): opened the Configure Recipe page with Description and Variations tabs.

Recipe page (As): most recipe configurations are accessible right on this page. Recipe Description is editable inline; Edit Alerts opens a dialog for recipe-level alerts; the Variable Sets tab allows adding and editing base and override variable sets; the Schedules tab lists all schedules and the variations that use them.

source code icon (B): opened the File Editor to edit the underlying recipe files.

File View (B): this option in the Recipe Actions drop-down list opens the File Editor.

duplicate recipe icon (C): opened the Duplicate Recipe dialog.

Copy (C): this option in the Recipe Actions drop-down list opens a similar Copy Recipe dialog.

trash can icon (D): opened a delete recipe confirmation dialog.

Delete (D): this option in the Recipe Actions drop-down list opens a similar Delete Recipe confirmation dialog.

Design Previews

Recipe Page: Variation Actions
Note that this update also introduces a new feature to rename variations!

The new **Variations** tab on the Recipes page offers users more quick actions for managing variations.

The new Variations tab on the Recipes page offers users more quick actions for managing variations.

Icon Identifies Ingredient Variations

Note that the first variation listed in the image above is marked with a diamond icon, indicating that it is enabled to be used as a recipe ingredient.

Ingredient settings were removed from recipe configurations but remain in a tab on each Variation page.

Recipe Page: Variable Sets

The new **Variable Sets** tab lists base variables defined in variables.json as well as override variable sets.

The new Variable Sets tab lists base variables defined in variables.json as well as override variable sets.

Recipe Page: Schedules

The new **Schedules** tab offers actions to add and edit schedules across variations that use them.

The new Schedules tab offers actions to add and edit schedules across variations that use them.

Other Fixes and Enhancements

  • Alert Emails Restored: The email alerting function in the platform was temporarily suspended during a transition to a new method for notifications. This issue was resolved immediately with a hotfix; the system sends alerts as expected. [DEV-6359]
  • Backup Events Removed from Kitchen Alerts: The kitchen-level Alerts feature included fields to set recipients for kitchen backup success/failure events. These alert settings have been deprecated due to low usage. See Alerts for more information on kitchen alerts. [DEV-6446]
  • Zero and Empty Test Variables Evaluate Properly: In some cases when users configured test variables with a value of "0" (zero) or "" (empty string), the system was evaluating these values as null. These tests, expected to fail, were passing because the system assumed that a null value was associated with a literal text string rather than a variable. This issue has been resolved with a code update to recognize zeros and empty strings as values. [DEV-6419]
  • File Compilation Errors State the Problem File: The error message generated for any file compilation problems did not include the name of the file causing the problem: "Error compiling file." This issue has been resolved by adding the filename to the messaging in logs or as displayed when users manually compile recipe files. [DEV-6145]
  • Order Run Fails Gracefully on Missing Docker Image Repo: Users found that if the notebook.json file in a container node had an empty "image-repo" field, an order run would hang rather than fail with a clear error message. This issue has been resolved with field validation to ensure that the Docker image repository name is not null and not an empty string. A new error message will be logged in the event that the system cannot locate the image repository: "<node>/notebook.json - Missing required configuration image-repo." [DEV-6347]
  • Delete Kitchen Function Handles Rollback Ingredients Properly: The rollback ingredients in the Delete Kitchen dialog was not matching those selected for the kitchen during kitchen creation. The rollback ingredients option allows users to clean up these resources during kitchen deletion. These issues have been resolved with code resets to ensure that rollback ingredients appear correctly during kitchen deletion. [DEV-5607, DEV-6100]

15 June 2020, 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 and 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]

8 June 2020, version 1.1.169

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • Kitchen Agents Settings Updated: In the DataKitchen platform, agents provide resources (disk space and memory) for order runs. During initial setup, customers decide whether to use the default agent pool hosted by DataKitchen or their own, private agent pools. In the case of a private agent pool, customers can also designate agent groups to segregate resources to specific kitchen environments. An agent group constrains the resources available to any one kitchen.
    DataKitchen engineers handle much of this configuration when setting up a new customer, so this release makes the following changes to the kitchen Agents tab. See Agents & Resources for more information. [DEV-5645, DEV-6334]
    • The Agent Constraint checkbox has been removed.
    • The Agent Group field is enabled for customers using a private agent pool with named groups.
    • The Agent Group field is disabled for customers using the default DataKitchen agents.
  • Node Description Updates are Saved: Users who updated graph node descriptions in the Node Editor without making any other edits to the nodes found that the system was not saving the new text. If they made any modifications in the same updates as the descriptions, the text saved correctly. This issue has been resolved and all changes to node descriptions are properly saved. [DEV-6185]
  • Documentation Added for Alerts: A UI feature for configuring alerts at the kitchen level was released recently but never documented. A new topic in this documentation describes how to use kitchen alerts and how they work with alerts set at the recipe level. See Alerts for the full content. [DEV-6098]
  • Fast-Throughput Graph Processing Updated: Following the release of a configurable option to change the order of execution for graph processing, users found specific scenarios where the nodes did not process as expected. These issues have been resolved, and the new fast-throughput execution works as designed. See Graph Order of Execution for more information. [DEV-6375, DEV-6418]

1 June 2020, version 1.1.168

FEATURE HIGHLIGHTS

DataKitchen Implements New Session Timeout Rules

Previously, users who logged in to the DataKitchen platform user interface had a maximum of four hours to work before their user sessions would automatically end. This session timeout occurred regardless of any user activity. As a result, users were in danger of losing the work they were doing in building recipes.

With this release, DataKitchen shortens the UI session length but restarts the session clock with user activity. Users will now be logged out after 2 hours and 10 minutes of inactivity. Work in progress is not saved. See User Sessions for more information. [DEV-4614, DEV-6335]

User Session Summary

  • Session max length: 130 minutes
  • Session clock: Resets with user activity
  • Work in progress: Not saved at session timeout

Other Fixes and Enhancements

  • Default Config Standardized for Container Nodes: When a user added a container node to a graph, the General Purpose Container and other DataKitchen container images supplied an empty config.json file. While this initial state provided flexibility for experienced script-writers, it prevented many users from building recipes quickly. An enhancement in this release sets a standard template for the container config with the following default fields. See config.json in the General Purpose Container topic for more information and field definitions. [DEV-5584]
{
    "apt-dependencies": [ ],
    "dependencies": [ ],
    "keys": {
        "run_script": {
            "script": "",
            "environment": {},
            "parameters": {},
            "export": [ ]
        }
    }
}
  • Schedule Parses Cron Strings Correctly: Users found that when they scheduled orders using certain cron expressions in variations.json via the File Editor, the variation's Schedule tab in the UI was not showing the proper settings. The tab did not set the schedule as "Advanced" for the cron expression; it left some fields blank; and it indicated that changes still required an update. If users clicked the Update button, the system removed the schedule completely and all future orders would run only once. This issue did not affect any existing schedules.
    This issue has been resolved in this release by updating the schedule editor to parse the cron expression for the form field entries and detect an advanced schedule setting, as shown in the following image. [DEV-6336]

26 May 2020, 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.

New Graph Processing Available

The new sequential graph processing is turned off by default but can be turned on by request.

See the Graph topic 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.

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.

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 and 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]

18 May 2020, version 1.1.166

FEATURE HIGHLIGHTS

Default Icons Added to Container Node List

A recent enhancement allowed users to choose among default images or upload custom images to represent their container nodes. With this release, the platform offers more than 35 Docker-based images in the default drop-down list. See Manage Container Icons for more information. [DEV-5874]

The platform expands the number of default container node icons.

The platform expands the number of default container node icons.

Other Fixes and Enhancements

  • Web App Runtime Performance Improved: This release completes a series of source code refactoring in the DataKitchen Web App to improve the runtime performance. No behavior or functionality has been changed. [DEV-6043, DEV-5727]
  • UI Shows Compiled Built-In Variables: The platform offers a number of system variables, such as RecipeName, for use in recipe configurations and kitchen overrides. While the system correctly applied these variables in order runs, the Run Variation dialog in the UI was not compiling the values. This issue has been resolved; the system variables display to the user as compiled. [DEV-4482]
  • Scheduled Orders Run Following Error: When a scheduled order failed on an atypical error, the schedule would stop and the system would not run the order at the next scheduled time. This issue has been resolved; scheduled orders encountering an error will run again at the expected intervals. [DEV-6242]

11 May 2020, version 1.1.165

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • Users can delete kitchens with numerous order runs: Users attempting to delete any kitchen that contained hundreds of order runs found that the delete request failed. The system generated an "unexpected server error" message. This issue has been resolved with an update to the deletion process to prevent timeout errors. [DEV-5807]
  • Error clarifies resource issue during scheduling: When scheduling an order, a user can allocate disk space and memory for running that order. Previously, if the user configured resource usage that exceeded the resources available for a single agent, the system did not complete the schedule and did not notify the user of the problem. This issue has been resolved with a warning message about "not enough allocatable resources." [DEV-5373]

Order Resources

Generally, the default resource allocations for an order are sufficient. The defaults are 1024 MB memory and 2048 MB disk space.

4 May 2020, version 1.1.164

FEATURE HIGHLIGHTS

Users Can Select or Add Custom Icons for Container Nodes
DataKitchen DataOps Platform WebApp users who are adding or editing container nodes to their recipe variations, can now select from a list of available icons to represent their container nodes.

Previously, the platform only offered a generic Docker "whale" icon, but with this release users can choose among other default images or upload their own custom images. More default images will be added in a future release. See Manage Container Icons for more information. [DEV-5164, DEV-5872]

New Delete Kitchen Dialog
This release offers a refresh of the Delete Kitchen wizard! The multi-step wizard has been replaced with a single confirmation dialog that contains all relevant settings. See Delete a Kitchen for more information. [DEV-3376]

Delete Kitchen is Permanent!

Reminder: When you delete a kitchen, you delete all configurations, orders, and secrets associated with that kitchen. The delete action cannot be undone.

Other Fixes and Enhancements

  • Support ended for Python2: Users who install the DKCloudCommand using Python2 and pip will receive an error message. Users must install the CLI using this syntax: pip3 install DKCloudCommand. [DEV-6117, DEV-5936]
  • New Jinja functions added for variable declarations: With this release, users can take advantage of two more built-in Jinja functions for variable transformation. [DEV-6022]
        "file_path": "/etc/asdf"
         "file_name": "{{basename(path)}}"
         "file_directory": "{{dirname(path)}}"
    
    • basename: returns the last name of a file path, as in /etc/asdf
    • dirname: returns the directory from a path, as in /etc/asdf
  • Remove variable function fixed: Recently, users found that when they removed variables from the Kitchen Overrides screen, the override values were not deleted and the variable names no longer mapped to the proper values. This issue has been resolved; when users remove variables, both names and values are deleted. [DEV-6188]

27 Apr 2020, version 1.1.163

FEATURE HIGHLIGHTS

Source/Sink Selection Available During Create Container
Users can now add a data source and data sink while creating a new container node. This enhancement adds these optional drop-down list fields to the Container option in the Add Node sidebar. See Create a Container Node for more information. [DEV-5823]

Other Fixes and Enhancements

  • Users can stop a resumed scheduled order run: When a scheduled order run failed and the user resumed the run, the platform did not allow the user to stop the next scheduled run. This issue has been resolved with an update in how the system checks for manual and scheduled jobs. [DEV-6070]
  • Status field removed from API responses: The status parameter has been removed from all API responses as it was redundant information. The API response codes already provide the status, where a 200-series code means success and any 400-series code indicates failure. [DEV-6044]

20 Apr 2020, version 1.1.162

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • Users can duplicate new nodes: When a user created a new graph node then added a second node as a duplicate of the first, the system generated an error because the first node had not yet been saved. This issue has been resolved by allowing users to duplicate new nodes even before the user clicks to Update the graph. [DEV-5937]
  • Update button works properly in File Editor: When users made recipe changes in the File Editor view and clicked the Update button once, the Update button would not activate or deactivate correctly with their subsequent changes or reverted changes. This issue has been resolved, and the button performs as expected. [DEV-5993]
  • Folder delete function updated: Users found that after deleting a node from a graph, they could not delete the node folder in the File Editor. This issue occurred when a user selected Delete from the folder drop-down list and checked Remove node from variation graphs in the Delete Node confirmation dialog. This issue has been resolved; the File Editor deletes folders properly when the associated nodes are no longer present in the graph. [DEV-5992]
  • Checks for available resources do not affect UI performance: When users clicked the Agent Status button multiple times to view available memory and disk space resources, the platform UI would become unresponsive. This issue has been resolved with a timeout added to these resource queries. [DEV-6014, DEV-6015]
  • Invalid kitchen error added to order-list command: The DKCloudCommand interface issued a "no orders found" error message when users passed an invalid kitchen name as an option for the order-list command. This message has been updated to provide better context: "The Kitchen <kitchen_name> was not found. The Kitchen may not exist, or you may not have kitchen-staff permissions." [DEV-1310]
  • Single email sent for duplicate alerts: When a user configured the same email address at both the kitchen and recipe levels to receive alerts for all events in an order run, that email recipient would receive two emails per event. This issue has been resolved by preventing the duplicate notifications. [DEV-5779]
  • Order run alert emails resumed: Recently, the system suspended alert emails for order runs due to a code conflict. This issue has been resolved, and users will receive emails as expected. [DEV-5974]
  • Error logging improved for SFTP connections: When a user entered an invalid host name or credentials for an SFTP data source or data sink and then ran the variation, the system logged a generic "unexpected error" message. The error messaging has been updated to report an invalid host, an unreachable host, or invalid credentials. [DEV-5978]

6 Apr 2020, version 1.0.161

FEATURE HIGHLIGHTS

Stay tuned for new DataKitchen features in coming releases!

Other Fixes and Enhancements

  • Users can add and select container node icons: Previously, when a user added a container node to a recipe graph, the default Docker icon displayed on the node when the graph was viewed in the Node Components mode. Now, users can select from multiple icons or add their own when creating or editing container nodes. [DEV-5164]
  • Order runs resume at failed node: Users found that when they resumed failed order runs, they were starting from the first nodes rather than the nodes where the previous runs failed. This issue was caused by a code refactor and has been resolved. Resumed order runs start at the failed nodes as expected. [DEV-5955]
  • New schedules are visible without refresh: When users created new variation schedules in the Schedule tab of the UI then added new variations to the recipe, those new schedules were not available to select in the Schedule drop-down list of the Add Variation dialog. This issue has been resolved; the platform makes new schedules available immediately for new variations. [DEV-5789]

Previous Releases

At this time, the notes from previous releases are available as internal DataKitchen resources only.

Updated 5 days ago

Product Releases


Release notes for user-facing fixes and enhancements in the DataKitchen DataOps platform

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.