Skip to content

Add bricefotzo/dbt-bqai package - #437

Open
bricefotzo wants to merge 1 commit into
dbt-labs:mainfrom
bricefotzo:patch-1
Open

Add bricefotzo/dbt-bqai package#437
bricefotzo wants to merge 1 commit into
dbt-labs:mainfrom
bricefotzo:patch-1

Conversation

@bricefotzo

@bricefotzo bricefotzo commented Jul 29, 2026

Copy link
Copy Markdown

Description

dbt-bqai is a package that wraps the BigQuery AI.* function family: AI.GENERATE, AI.GENERATE_BOOL/INT/DOUBLE, AI.CLASSIFY, AI.SCORE, AI.IF, AI.EMBED - so they can be called from dbt models without repeating the connection, endpoint and model-parameter boilerplate on every call. Defaults are configured once via vars in dbt_project.yml and can be overridden per call.

It also ships two generic data tests (assert_valid_category, assert_embedding_dimension) for validating AI outputs, and defaults for Vertex AI cost controls (thinking_budget, max_error_ratio, optimized/embeddings path).

Link to your package's repository: https://github.com/bricefotzo/dbt-bqai

(Context: I first opened dbt-labs/hub.getdbt.com#4611 by mistake; @b-per kindly pointed me to the hubcap flow. Thanks!)

Checklist

Real world usage

  • (Required): I have been using this package in production and am satisfied with its behavior.

First run experience

  • (Required): The package includes a licence file detectable by GitHub, such as the Apache 2.0 or MIT licence.
  • The package includes a README which explains how to get started with the package and customise its behaviour
  • The README indicates which data warehouses/platforms are expected to work with this package

Customisability

  • The package uses ref or source, instead of hard-coding table references.

Dependencies

Dependencies on dbt Core

  • The package has set a supported require-dbt-version range in dbt_project.yml. Example: A package which depends on functionality added in dbt Core 1.2 should set its require-dbt-version property to [">=1.2.0", "<2.0.0"].

Dependencies on other packages defined in packages.yml:

  • Dependencies are imported from the dbt Package Hub when available, as opposed to a git installation.
  • Dependencies contain the widest possible range of supported versions, to minimise issues in dependency resolution.
  • In particular, dependencies are not pinned to a patch version unless there is a known incompatibility.

(the package has no packages.yml dependencies of its own)

Interoperability

  • The package does not override dbt Core behaviour in such a way as to impact other dbt resources (models, tests, etc) not provided by the package.
  • The package uses the cross-database macros built into dbt Core where available, such as {{ dbt.except() }} and {{ dbt.type_string() }}.
  • The package disambiguates its resource names to avoid clashes with nodes that are likely to already exist in a project. For example, packages should not provide a model simply called users.

Versioning

  • (Required): The package's git tags validates against the regex defined in hubcap/version.py (examples).
  • The package's version follows the guidance of Semantic Versioning 2.0.0. (Note in particular the recommendation for production-ready packages to be version 1.0.0 or above)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant