Looker 5.22 Release Notes


(Carter Moar) #1

Anticipated Deployment Dates

Release Rollout Begins: August 26, 2018
Release Final & Download Available: September 6, 2018

Release Highlights

In addition to general tweaks and enhancements, this release comes with new and improved features in the following categories. Read on for more detail.

Preparing for Release

Please take notice of items marked with a :zap: as they indicate changes to existing functionality and may require your attention. For more information see Features by Section below.

Notable Features

Merged Results Improvements

Looker users now experience even more front-end flexibility with Merged Results on experimental Custom Fields. Merged results are also now available in embedded iframes for Powered By Looker users.

Features by Section

Dashboards and Visualizations

  • Merged Results improvements:
    • :alembic: Experimental custom fields can now be used in Merged Results.
    • Merged Results are now available in embedded dashboards.
  • :alembic: Beta Enhanced Renderer. Introduced Enhanced Rendering designed to be used in conjunction with the beta Enhanced Visualizations feature. Learn more about customer-hosted setup.

LookML and Development

  • Code Quality Options. Added a third level of Code Quality requirements. Looker Admins can now allow developers to commit LookML code with Warnings but not Errors in the LookML validator. Learn more.
  • Git setup performance enhancements. Back end enhancements to the git setup process make git integration faster and more performant.
  • :zap: Disabled Legacy Feature: The “allow the access_filter_fields parameter” Legacy Feature has been disabled, but will remain available until Looker 5.26 if needed. Please use User Attribute-based access filters for controls going forward. Learn more.
  • :zap: Introduced a new Legacy Feature: Native Derived Tables convert dates and yesnos to strings by default. Learn more.


  • Athena. Updated to Athena driver 2.0.5 and introduced support for arrays in Athena.

General Tweaks and Bug Fixes

  • Dashboards, Visualizations, and Explore
    • :alembic: Continued improvements to the Enhanced Visualizations Labs feature.
    • Fixed a bug where pivots occasionally caused blank visualizations on the explore.
    • Fixed a bug where some Looks were unable to load more than 10000 rows.
  • Scheduling and Downloading
    • Fixed a bug where schedules occasionally failed due to node communication errors.
    • Fixed a bug where filters on fields that had been removed caused scheduler UI to break.
    • Fixed a bug where some schedules to S3 buckets were failing.
  • Platform and Administration
    • :zap: Fixed a bug where string type user attributes did not properly escape -.
  • LookML and Development
    • Addressed an issue where switching between files in the IDE was sluggish.
    • Fixed a bug where some distance dimensions incorrectly calculated a distance of 0.00.
    • Unnecessary include statements are now generated commented in view files.
    • :alembic: Fixed a bug where the Content Validator sometimes reloads with boxes checked.
    • :alembic: Continued improvements to experimental Custom Fields.
    • :zap: Fixed a bug where custom dimensions could be used to query filter-only fields. Looks and dashboards with these fields may cause an error message.
    • Fixed a bug where always_join was not used in suggestions query.
  • Content Management and Discoverability
    • Fixed a bug where the spaces sidebar was not scrolling properly.
    • Fixed a bug where restoring a dashboard from the Trash did not restore associate Looks.
    • Added breadcrumbs to the spaces page.
  • Dialects
    • Fixed a bug where number type dimensions did not recognize the decimal data type in Athena.
    • The LookML generator now double-quotes column references in IBM Db2.
  • Security
    • Removed stack trace exposure in the event of low-level errors.

(Carter Moar) #2

(Max Corbin) #3

test post, ignore plz :slight_smile:

(Dan Groman) #4

The chromium update didn’t fix out rendering issues. A follow up patch was applied that appears to have been resolved our issue with single value tiles.

(Carter Moar) #5

It sounds like the specific issue you’re referencing @dgroman1988 appears to be addressed in your conversation with @Ellio (with Looker 5.22.11+). For those following along at home, the new rendering Labs feature in Looker 5.22 (powered by chromium) gives us the foundation to build out cool new rendering features and better positions us to address issues going forward. It’ll start off with some things like rendered links and the ability to copy text with more currently expected to be available by the end of the year.

(Dan Groman) #6

Yes it sounds like we are going on two days of successful PDF exports where single value visualizations have not experienced issues.

We still have other issues regarding the PDF functionality. Not sure if any of these are to be addressed anytime soon. Happy to elaborate more offline if this information isn’t being relayed via our account manager.

(Carter Moar) #7

(Ian) #8

Where can this be changed:

  • Code Quality Options. Added a third level of Code Quality requirements. Looker Admins can now allow developers to commit LookML code with Warnings but not Errors in the LookML validator.


(Carter Moar) #9

It can be edited in the settings menu for a given project. You can get there by hitting the drop down arrow on the version control button while in the IDE. This doc has pictures, since they’re probably more helpful than me trying failing to put it in words: https://docs.looker.com/data-modeling/getting-started/setting-up-version-control#project_settings

(Ian) #10

Thanks for letting me know. I didn’t look there as I didn’t even consider is was project based, was looking around admin section.
We have 50+ projects with historical lookml (include *.dashboard) which I regularly have to explain the problem to people and dont fancy going through each project and resolving it/updating settings.