dbt-costgate v1.0.2
Changed
-
The line about a resource dbt-costgate does not price no longer says its one
fact twice. It read "country_codes changed but is not priced — seeds are not
priced". The first half now says what happened and the second says why:dbt-costgate: country_codes changed but is not in the report — seeds are not priced.Same for the
--selectform ("… was selected but is not in the report — …").
Grep foris not pricedstill matches; grep for the full old sentence does not.
It is also the more accurate wording for an ephemeral model, whose cost really
is priced — in the rows of the models that inline it.
Fixed
- A changed analysis is now told that "analyses are not priced", rather than
"analysiss are not priced". The plural was built by adding a letter. - A changed Python model's explanation no longer runs two dashes together.
It was "… is not priced — Python models are not priced — dbt-costgate
estimates SQL scans"; the second dash is now a semicolon.
Docs
- New: What dbt-costgate does not price.
Seeds, snapshots, tests, analyses, hooks, Python models and ephemeral models
get no row in the report, and the tool has always said so on stderr — but no
shipped page explained why, or what each one actually costs. The section names
all seven and is blunt about the part that matters: "not priced" is not
"free." A snapshot is aMERGEand a test is aSELECT; both scan real
bytes that dbt-costgate does not put a number on. Ephemeral models are the
exception — their cost is counted, in the rows of the models that inline them. - Materialized views and BigQuery scripts are now documented, in both the
usage accuracy notes and the explained-page caveats. Their siblings were
already there; these two were not. A materialized view's figure is the cost of
building it once, and BigQuery bills each automatic refresh on top. A model
usingDECLAREorBEGINreads low — the only caveat on the page that
errs that way — because BigQuery can only price the statements it can resolve
before the script runs.