Axi finds the value you name
Ask about Lyon, Acme or premium without saying where they live: Axi now finds the column that holds the value you name, checks how two tables join before combining them, and reads since when a column has data — while every look at your data stays within a set cost.
What changed
- The value you name, wherever it lives. When a question names a city, a brand or a status but not the column, Axi searches the columns most likely to hold it — case and accents ignored — and filters on the value exactly as stored. You see it as a step: Found “lyon” in customers.city.
- A column looked at before it's used. Axi reads a column's range, its empty values and its most frequent values — and for a date, the months it has data for and the ones it lacks — before choosing a filter or answering "since when".
- Joins checked, not guessed. Before combining two tables, Axi asks the engine how they join — along which keys — or why they don't, and what to do instead.
- What your warehouse says about a table. Axi reads how a BigQuery table is partitioned and clustered, when it was last loaded and how large it is — and knows which tables only answer queries filtered on a date, so its widgets and reads always carry one.
- Every look at your data has a ceiling. The value lists in the editors and Axi's value reads are read-only, stop after 20 seconds and, on BigQuery, bill at most 10 GB each; a large table partitioned by date is read over its latest 30 days of data.