[v5.0.0] Add query acceleration costs, incrementalize cost per query, account for new service type #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does the following:
cost_per_query
model changesmetering_history
instead ofwarehouse_metering_history
for consistencystg_metering_history
andstg_warehouse_metering_history
to re-process the last 7 daysstg_metering_history
, we need to add a new field that is part of the unique key,entity_id
. will require a full refresh.WAREHOUSE_METERING
service_type
we are seeing inrate_sheet_daily
cost per query reconciliations:
check that everything lines up, ✅
check account with QA enabled, costs line up if you remove QA ✅