Release Notes: Runner Version 3.4.5

Breaking Changes

None

Issues Resolved in this Release

Improvement

Issue

Summary

Description

Status

MIT-3436

Add CLI for non_personal_api_key (uploading files) (MIT-3408)

Runner 3.4.4 introduced functionality to accept log or diagnostic data upload via pre-authenticated webhooks. The configuration of this was originally implemented in the Mitto database only, requiring direct database updated. This change implements a command line interface (CLI) to support configuration of this feature.

Done

MIT-3426

Create PDF exports using Tableau REST API instead of ‘vizql’ API

A Tableau authentication change is preventing REST API PAT tokens to authenticate to the non-REST APIs (VizQL) used to export dashboards. This required changes to the Runner Tableau Export jobs, where reliance on VizQL is removed. The Tableau Export jobs are now using the Tableau REST API only.

In Testing

MIT-3306

JSONL inputter add support for relative path

The JSONL inputter for “JSON Lines” was unable to use RegEx for source file selection. This has been implemented, bringing support for RegEx input file selection to JSONL files to parity with the other flat file inputters.

In Testing

Bug

Issue

Summary

Description

Status

MIT-3439

Update apitoolbox

Runner’s APIToolbox version requirement was updated to 0.14.1

Done

MIT-3437

LicenseRefreshBackgroundTask stops on failure

The background process to retrieve licensing information would fail if an error was encountered, causing the service itself to fail. This changes that logic to log the error and continue, allowing the background process to continue.

Done

MIT-3434

engine_kwargs are removed after initial insert “batch”

An error in the handling of a job’s engine_kwargs on the output section caused the fast_executemany parameter to re-default to True despite the configured option in the job. This would be seen on the second batch insert to the destination table. The reverting of the fast_executemany option to True would cause some jobs writing to MS SQL Server to fail. This issue is now corrected.

Done

MIT-3419

Store button on jobs page (visibility / click handling) broken

The “Store” button on the Job pages was shown in all cases, including jobs with no Store. This is now changed to conceal the Store button when no Store is in use for a Job. In addition, an error prevented navigation using the Store button. These issues are now resolved.

In Testing

MIT-3416

Data adaption to MS SQL Server - not applying varchar to nvarchar change when adapting data output to existing table/varchar column

When data sampling determined that a VARCHAR column on an existing destination table in MS SQL Server needed to be changed to NVARCHAR (for storage of unicode data), this change was not occurring properly. This is resolved.

In Testing

MIT-3411

Temporary store consumes available storage: could not extend file... No space left on device

There is a possibility that large IO jobs will consume available filesystem space when the temporary store grows too large. To rectify this, there’s an added option to use gzip compression on the temporary store. This is set by the environment variable TMP_STORE_STRATEGY, with options of FILE (the default, uncompressed) or FILE_GZ (compressed).

In Testing

MIT-3361

MS SQL Server: Unicode error on sample.py when record includes bytes

Records stored to MS SQL Server with columns including raw bytes values will in some cases fail due to invalid detection of bytes data as JSON, resulting in a unicodeerror. This is corrected by setting the destination column datatype as NVARCHAR. Runner now makes this change to NVARCHAR when required.

In Testing