New LookML Runtime provides faster LookML validation and content validation, more performant loading of Explores and dashboards, and faster SQL query writing, among other performance improvements.
You can use the
new_lookml_runtime parameter to override your Looker instance's default LookML runtime. The default runtime for projects on your instance is configured with the Use Legacy LookML Runtime legacy toggle:
- If the Use Legacy LookML Runtime legacy feature is enabled, projects on the instance will use the legacy LookML runtime by default. LookML developers can add
new_lookml_runtime: yesto a project to override the instance default and enable New LookML Runtime for the project.
- If the Use Legacy LookML Runtime legacy feature is disabled, projects on the instance will use New LookML Runtime by default. LookML developers can add
new_lookml_runtime: noto a project to override the instance default and use the legacy LookML runtime.
For example, if the Use Legacy LookML Runtime legacy feature is disabled for your instance, you can add the
new_lookml_runtime: no statement to the project's manifest file to use the legacy LookML runtime for the project:
If your project does not have a manifest file, you can create one using the Looker IDE.
When New LookML Runtime is enabled for a project, the LookML validator may catch previously overlooked errors. See the Error: Unknown or Inaccessible Field Best Practices page for more information on how to resolve these errors.