Looker 6.4 Release Notes

done
file
normal_priority

(hilary) #1

Release Rollout Begins: January 13, 2019
Release Final & Download Available: January 24, 2019

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 the Legacy Feature Updates and Features by Section below.

Experimental and Beta Features

The following new and improved experimental and beta features are marked with a :alembic::


Notable Features

User session Configurations

Looker Admins have more control than ever over their users’ sessions. Set a default session length of your choosing and decide whether users are able to log in concurrently.

More Powerful Color Palettes

New color collections and an easier-to-use color picker allow users to have more control over the appearance of their visualizations. Looker Admins are now able to create and manage custom color collections.

Mixed-Type Stacked Charts

Visualize your data with more flexibility with stacked mixed-type cartesian charts. Users are now able to view and save content with several series types stacked on top of one another, creating a more dynamic and clearer data visualization experience.

45%20PM


Features by Section

Dashboards, Visualizations, and Explore

  • :zap:Enhanced Rendering out of Beta. Enhanced Rendering is now out of Beta and turned on by default for all instances. To continue using PhantomJS to render PDFs, please utilize the Legacy Rendering legacy feature. Learn more.
  • Mixed-type stacked charts. Cartesian charts using mixed series’ types can now be stacked. Learn more.
  • New and custom color collections. New color palettes and color collections allow for more color customization on visualizations. Learn more.
  • Easier-to-use color palette selector. Visualization menu improvements make color selection easier and more straightforward. Learn more.
  • More powerful conditional formatting. Finer control over color-value mapping. Learn more.

Platform and Administration

  • :alembic: Beta Homepage Updates. Updates to default Looker homepage with end-users in mind.
  • Customizable session length. Looker Admins are now able to customize default session duration for users. Learn more.
  • Option to disable concurrent sessions. Looker Admins are now able to disable concurrent user sessions. Learn more.

LookML and Development

  • :alembic: Content Validator performance improvements. Significant performance improvements to the Content Validator.
  • :alembic::zap: Project Import syntax change. include statements for files from imported projects now require the following syntax: include: "//<INCLUDE_FILE_PATTERN>. Use of a single-slash will now produce a warning.
  • New API Endpoints: deploy_to_production and :alembic:content_validation

Embedded Analytics

  • :alembic: Beta Embed Theme Editor. Looker Admins are now able to set themes for embedded content. Learn more.

  • New embedded javascript event: drillmenu:click. Embed developers will now be able to receive Javascript event notifications of drill menu clicks in iFrame embedded contexts. Learn more.

Dialects

  • Introduced Support for Denodo 7.0
  • :zap: Driver upgrades: MariaDB (2.3.0), PrestoDB (0.214), and PostgreSQL (42.2.5)
    • MongoBI users will need to remove the maria15x entry from their custom JDBC YML files in order for Looker to start. Learn more.

Security

  • :zap: Resolved an issue where PostgreSQL and Amazon Redshift connections were not verifying SSL certificates.
    • It’s possible that previously silent verification issues may appear upon update.
    • In cases of SSH tunnels certificate validation is likely not necessary and could produce warnings.

General Tweaks and Bug Fixes

  • Dialects
    • Fixed a bug where the Week Duration dimensions generated incorrect SQL in BigQuery.
  • Administration and Platform
    • Fixed a bug where connection test for BigQuery hung after uploading new .p12 file.
  • Dashboards, Visualizations, and Explore
    • Fixed a bug where filter values overflowed the filter input box.
    • Fixed a bug where the table calculations button sometimes did not appear when expected.
    • Fixed a bug where drills did not work in some Single Value Visualization tiles.
    • Fixed a bug where the text area model did not render properly.
    • Fixed a bug where value labels did not appear on stacked column charts.
    • Fixed a bug where “Explore From Here” page on dashboards did not include filtered custom dimensions.
    • Fixed a bug where Funnel Visualizations were rendering incorrectly.
    • Fixed a bug where long horizontal axis labels overlapped.
    • Fixed a bug where navigating to PDT Admin panel sometimes produced a 500 error.
  • LookML and Development
    • The IDE now supports uppercase characters in LookML file names.
    • New LookML validator warnings for invalid characters.
    • Fixed a bug where results downloaded from SQL runner had arbitrary file names.
    • Fixed a bug where duration fields didn’t work as drill fields or when referenced in measures.
    • Fixed a bug where some users were unable to “Explore From” a SQL Runner query.
    • Fixed a bug where some SQL Runner queries could not be cancelled.
  • Scheduling and Downloading
    • Conditional formatting is now retained in XLSX downloads.
    • Fixed a bug where “Send if there are results” did not work with “All Results” selected.
    • Fixed a bug where it was not possible to send visualizations from explores.
    • Fixed a bug where downloading data from a dashboard did not use correct timezone.
    • Fixed a bug where downloading results from SQL runner opened results in new browser window instead.
    • Fixed a bug where embedded user-defined dashboards ignored filters when scheduling and sending.

Click events when a user downloads a report PDF or CSV?
(hilary) pinned globally #2

(Erik) #3

Does it mean that we can set our own Min/Mid/Max?


(Arielle Strong) #7

Hi Erik, that’s correct! You will now have much greater control over setting a min/mid/max, stepping colors, and mirroring the color range around a value.


(Kyle Rourke) #8

Any more details on the specifics?h


(Michael Jalkio) #9

Hi @arielle, has the content_validation endpoint been added to the API documentation? I’m not sure what section it would be a part of.


(conrad) #10

@mjalkio the api documentation is updated with the content_validation endpoint. It can be found in the Content section.


(Michael Jalkio) #11

I don’t see anything on https://docs.looker.com/reference/api-and-integration/api-reference/content, is this the correct page @conrad?


(Izzy) #12

I think @conrad might be referring to the interactive API docs contained within the Looker product, accessible by default at https://your.looker.com:19999/api-docs/index.html. I’m also not seeing a reference to the endpoint in the docs on docs.looker.com yet, but there does seem to be documentation for it in the interactive docs:


(conrad) #13

Apologies for the miscommunication. Thanks @mjalkio for bringing this to our attention and @izzy for the clarification. I’ll work with our docs team to get the online documentation updated.


(erin.alexander) #14

Hi @mjalkio, Erin from Docs here. As Izzy mentioned, you can go to https://<your-looker-host-name>:19999/api-docs/index.html to see the Interactive API Documentation and Explorer. Please note that the new content_validation endpoint is for API 3.1, so please select the 3.1 version:


(Michael Dunn) #15

It looks like there might be a bug in rendering the dropdown “Explore” menu. There’s one explore that is supposed to be listed under Ω BI Internal, and if the dropdown box used all available viewport height, it would render it fine, but it doesn’t, yet it also doesn’t render a scroll bar.

(It’s a tall image - you’ll need to click on it to see the full height.)

My hypothesis is that the decision for whether not to include a scroll bar is determining how much space is needed to list all the explores and comparing that to the height of the viewport, but the dropdown’s maximum height is limited to viewport height minus n.

We see more evidence for this being the case, in that when the window (and therefore the viewport) height is reduced to a point where the scroll bar does appear, and then one scrolls all the way to the bottom, this is observed:

image

Observe that the bottom of what’s supposed to be visible still isn’t, but more importantly, observe that the bottom of the scroll bar isn’t visible either.


(Izzy) #17

Interesting, I’m not seeing this in my quick test. What OS/browser combo are you seeing this in?

Also, just to make sure— can you still scroll and access the explore, and this is just a visual bug, or is it actually preventing you from accessing it?

Let me know what browser and os this is on and I’ll pass it along to the engineers.


(Michael Dunn) #18

This is on Chrome 71.0.3578.98 on MacOS 10.14.3

It can’t scroll any further, because the scrollbar is already at the bottom; it’s just not rendering that far down. I have to resize the window to make the bottom explore visible.


(Izzy) #19

I revisited this and though I’m not getting hidden explores, I see what you mean about the scrollbar and totally believe that’s happening. I’ve documented it + filed with the appropriate bug exterminators on our end! Enjoy your shiny new Entomologist badge :slight_smile:


(Izzy) #20

We’ve fixed this issue with the scrollbar, thanks for the report Michael! It looks to me like you’ve been updated to the newest version that should contain the fix, so let me know if you’re still seeing that happen.