You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of October 2022 (per the release notes), a new incremental_mar table is syncing as a result of the Fivetran Log connector.
This new table stores the incremental daily active rows for every destination, connector, and table within your account. This is helpful in tracking and managing consumption in our new pricing model.
The Fivetran Log should factor this new table into the calculations used in the downstream models. Additionally the active_volume model will be deprecated and should be soon swapped out in place of this new source table.
Describe alternatives you've considered
No current alternatives. We will want to swap to this table in the future as a result of deprecation of the active_volume table.
Are you interested in contributing this feature?
Yes.
Yes, but I will need assistance and will schedule time during your office hours for guidance.
No.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing feature request for this?
Describe the Feature
As of October 2022 (per the release notes), a new
incremental_mar
table is syncing as a result of the Fivetran Log connector.This new table stores the incremental daily active rows for every destination, connector, and table within your account. This is helpful in tracking and managing consumption in our new pricing model.
The Fivetran Log should factor this new table into the calculations used in the downstream models. Additionally the
active_volume
model will be deprecated and should be soon swapped out in place of this new source table.Describe alternatives you've considered
No current alternatives. We will want to swap to this table in the future as a result of deprecation of the
active_volume
table.Are you interested in contributing this feature?
Anything else?
No response
The text was updated successfully, but these errors were encountered: