Looker 5.8 Extended Support Release Notes

release

(Carter Moar) #1

Expected Deployment Dates:

ESR Staging: March 4, 2018 - March 31, 2018
ESR Production Release: April 1, 2018 - June 23, 2018


Release Highlights

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.

Several Legacy Features that were previously disabled have now been completely removed. Please see the Legacy Feature End-of-life Schedule for more detailed information.

Legacy Feature Removals

Notable Features

Action Hub

Whether you want to move data out of Looker into another app, or simplify your ETL process, the new Action Hub is your one stop shop for pre-built integrations. Replacing the “Integrations” tab in the Admin panel, the Action Hub makes integrating your data sources simpler, faster, and more straightforward. Integrations now available with Airtable, Segment, Twilio, Slack, JIRA and more.

Content Sidebar for Admins

For Looker Admins who want an easier way to communicate with end users, introducing the curatable “From Your Company” content sidebar on the Looker Homepage. The customizable sidebar supports images, links, and markdown text.

Jump to File

LookML developers can now easily switch between LookML files within a given project from the IDE, making LookML development a faster, more seamless experience. Need to work quickly switching between Model and View file? No more searching - a quick command + J brings up the search function to help you navigate to the next file in seconds.

Features by Section

Action Hub

  • Introduced the Looker Action Hub and some great integarations (Airtable, AWS, Azure Storage, Digital Ocean, Hipchat, JIRA, SendGrid, Slack, Tray, Twilio, Zapier joining Segment). Learn More.
  • :zap:Changes to Segment integration. User who have previously used Segment integration will need to accept new terms of service before continuing to use this feature.

Dashboards and Visualizations

  • :zap: Dashboard Tile Defaults. Changed default size and placement of new Dashboard elements to make editing multi-element Dashboards easier. Learn more.
  • Lookless Dashboard Conversion. Improved usability of Dashboard conversion modal.

Content Management and Discoverability

  • Curatable Content Sidebar for Admins. Admins are now able to create and curate a sidebar on the Looker homepage that allows them to communicate with Looker users in their organization. Learn More.
  • "Recently Viewed" Content on Homepage. “Recently Viewed” content can be organized by user group, allowing admins to track content use.
  • Content Validator Performance. Decreased time for complete validation in Content Validator.
  • LookML Dashboards Space is no longer displayed in the Browse drop-down when there are no Dashboards in the Space.

Data Delivery

  • Dashboard CSV ZIPs. It is now possible to deliver zipped .csv files from Dashboards via schedule and Send Now.
  • :zap: Public Looks no longer support row limits of more than 5,000. Larger result sets will be truncated at the lesser of the saved row limit or 5,000 rows.
  • :zap:Increased the size of images in scheduled emails. Look and Dashboard images embedded in scheduled emails no longer have a fixed width.
  • :zap:Completely removed Legacy Features.

LookML and Development

  • :zap: Renamed Push and Pull in Developer Branch git options menu in IDE to Push and Pull Remote Changes for clarity.
  • :zap: The LookML Validator now correctly warns when Dashboard filters have empty, unnecessary, or unknown parameter declarations. Until addressed, these warnings may prevent committing new LookML changes if the Code Quality feature is enabled.
  • Jump to File. It is now possible to search for LookML files by name from within the IDE. Learn more.
  • Example Datagroups. Added example datagroup parameters to newly-generated projects. Learn more.

Platform and Administration

  • Clarified Connections page. Updated the Connections page to make it more apparent that the Maintenance Schedule applies to both Persistent Derived Tables and Datagroups.
  • Added option for administrators to disable “Persistent Sessions.” Learn more.
  • :zap: Replaced the Delete button with the Disable button on User Management page to reduce the risk of accidental user deletion. Learn more.
  • :zap: Fixed a bug with the see_user permission in closed system configurations. Non-Admin users on closed systems with the see_user permission are now able to see all looker users rather than those in their same user group.
  • :zap: Completely removed Legacy Features.
  • :alembic: Prepend SQL Comment. Added an experimental labs feature that prepends a comment to outgoing SQL queries for tracking. Learn more.

Dialects

  • Turn off ORDER BY in API Queries. Introduced the option to turn off sorts for downloaded and API queries for users on Hive-based databases.
  • Added Qubole Presto streaming capability.
  • Introduced support for Date/Time partitioned columns in Google BigQuery. Learn more.
  • Database views in Vertica now appear in SQL Runner.

Security

  • Fixed issues where MySQL, Snowflake, and MariaDB drivers had elevated file system access.

(Camille Vernon | Data Operations Analyst) #2

Hi!

I clicked and read the linked article, and I am still not sure what this is in reference to – what does it mean to coerce a dimension to a measure?

Thanks!


(Carter Moar) #3

In the old world, a field declared as dimension: some_dimension could appear as a measure. This would happen when the field referenced a measure, as in the example below. Looker silently converted such dimensions to measures. The reason Looker did this coercion is that a dimension referencing a measure would create invalid SQL; non-aggregates cannot reference aggregates.

measure: some_sum {
  type: sum
  sql: ${TABLE}.value ;;
}

dimension: some_dimension {
  type: number
  sql: ${some_sum} ;;
}

The old behavior was confusing to developers and end users and could cause issues and unexpected behavior. We now produce a warning when you do this, but for older instances (those created before Looker 3.54) the functionality followed the phase-out plan described here.


(Camille Vernon | Data Operations Analyst) #4

Thank you! Explanation much appreciated!!