LogoLogo
  • Introduction
    • Overview
    • Why Alvin?
    • Connect your systems
      • Data Warehouse
        • BigQuery
          • Provision source system credentials
          • Provision with GCloud CLI
        • Snowflake
        • Databricks
      • Business Intelligence
        • Looker
      • Orchestration
        • dbt
      • SSO (Single Sign-On)
    • Security & compliance
    • Types of metadata
    • FAQ
  • Cost Monitoring
    • Introduction to Cost Monitoring
    • Compute
    • Storage
  • BI Query Optimizer
    • Introduction to Query Optimizer
    • How does it work?
    • Getting started
  • Workflow automation
    • Introduction to Workflow Automation
    • Events definitions
    • Configuring Workflows
  • Anomaly Detection
    • Anomaly Detection
  • Exploring Metadata
    • Lineage
      • Depth of lineage
    • Impact Analysis
    • Entities
    • Entity View
    • Metadata Warehouse
Powered by GitBook
On this page
  1. BI Query Optimizer

How does it work?

PreviousIntroduction to Query Optimizer NextGetting started

Last updated 4 months ago

What is the Query Optimizer and how does it work?

  • The Query Optimizer is a layer that sits between BigQuery and Looker (or any other client like python or java) connecting to the . This can be tested and validated by changing the API host i.e in the .

  • The proxy implements all functionality of the BigQuery API, in fact it passes most API calls forward and only interacts with SQL payloads.

  • At the moment, the proxy is focused on optimizing analytical workloads (i.e SELECT statements), but there is also a roadmap for it to be further developed to optimize data pipelines (dbt, airflow etc).

BigQuery API
BigQuery Python Client