fivetran/dbt_fivetran_log

Issues

• [Feature] Update package to use new `extract_summary` event instead of currently-being-deprecated `api_call`

  #137 opened a month ago by fivetran-jamie
  0

• [Documentation] Move badges below H1 heading

  #139 opened a month ago by fivetran-joemarkiewicz
  0

• [Feature] Update Data Models to Coincide with Connector Changes

  #129 opened 7 months ago by fivetran-joemarkiewicz
  1

• [Version Update] dbt 1.8 introduced renaming of tests to data_tests

  #133 opened 2 months ago by JustMaris
  4

• [Feature] Provide deleted status for deleted connectors within connector_status model

  #108 opened 6 months ago by fivetran-joemarkiewicz
  2

• [Feature] Update docs to make clarify sync times

  #128 opened 6 months ago by fivetran-reneeli
  1

• [Bug] Possible Duplicates in Audit Table Model

  #131 opened 7 months ago by fivetran-joemarkiewicz
  0

• [Bug] `fivetran_log_json_parse.string_path` arg should be an array in `fivetran_platform__audit_user_activity` model

  #124 opened 7 months ago by fivetran-jamie
  0

• [Feature] make staging `log` model an append-strategy incremental table

  #82 opened 2 years ago by fivetran-jamie
  2

• [Feature] Audit user activity

  #89 opened 8 months ago by fivetran-elijahdavis
  0

• [Bug] Databricks SQL Warehouse Compatibility

  #120 opened 9 months ago by fivetran-joemarkiewicz
  2

• [Bug] String/List Agg Fields in Connector Status model result in error if they exceed limits

  #118 opened 9 months ago by fivetran-joemarkiewicz
  1

• [Bug] JSON parsing error in Redshift

  #113 opened 10 months ago by fivetran-reneeli
  1

• [Bug] Recursive issues

  #84 opened a year ago by dioptre
  6

• [Bug] unique_fivetran_platform__audit_user_activity_log_id not using log composite key

  #100 opened a year ago by kieronellis
  5

• [Bug] empty `credits_used` table causing date-casting error in `fivetran_platform__usage_mar_destination_history`

  #104 opened a year ago by fivetran-jamie
  0

• [Bug] Error parsing JSON in model for auditing user activity

  #105 opened a year ago by andysteinitz
  9

• [Feature] Support for SQL Server

  #94 opened a year ago by fivetran-joemarkiewicz
  1

• [Feature] Support for Fabric

  #103 opened a year ago by itsalljustdata
  2

• [Feature] Deprecate Transformations and Trigger Staging Model and Downstream References

  #93 opened a year ago by fivetran-joemarkiewicz
  0

• [Bug] Failure of Fivetran Platform Connector dbt Quickstart Transformations

  #95 opened a year ago by rwalker-bhep
  0

• fivetran_platform__audit_table.unique_table_sync_key definition should include "schema_name"

  #90 opened a year ago by abine-michael-planting
  7

• [Bug] Version 1.1.0 Breaking in Postgres

  #91 opened a year ago by bcutler2919
  16

• [Bug] Failure in test in one of fivetran_logs model.

  #88 opened a year ago by Sunnyinho
  11

• [Feature] totally deprecate `account_membership` table

  #83 opened a year ago by fivetran-jamie
  0

• [Feature] Add sync_id to stg_fivetran_log__log

  #78 opened 2 years ago by camcyr-at-brzwy
  5

• Bug - fivetran_log__connector_status.sql failing with large sets of logs

  #56 opened 3 years ago by fivetran-juliengoulley
  3

• [Bug] Runtime Error in `does_table_exist` macro

  #75 opened 2 years ago by dimoschi
  5

• [Feature] Add connector_id to incremental_mar table

  #76 opened 2 years ago by pkanter
  1

• [Bug] Duplicated months in fivetran_log__mar_table_history

  #73 opened 2 years ago by simon-stepper
  11

• [Bug] Fivetran UI data differs from Fivetran Log data

  #63 opened 2 years ago by JadAbdallah
  32

• [Feature] Support the new INCREMENTAL_MAR table

  #65 opened 2 years ago by fivetran-joemarkiewicz
  0

• [Bug] `stg_fivetran_log__log` sometimes failing unique test

  #71 opened 2 years ago by fivetran-catfritz
  1

• FEATURE - schema changelog incremental materialization

  #33 opened 3 years ago by fivetran-jamie
  1

• FEATURE - expand database compatibility to postgres + databricks (postgres done)

  #25 opened 3 years ago by fivetran-jamie
  1

• BUG - unable to install dbt v0.20.0 because of dbt utils fishtown v0.6.6 dependency

  #21 opened 3 years ago by edbizarro
  2

• BUG - fivetran_log__connector_status.connector_health = broken for a connected connector

  #23 opened 3 years ago by ipear3
  9

• BUG - fivetran_log__audit_table should be partitioned

  #27 opened 3 years ago by CraigWilson-ZOE
  4

• BUG - dbt hub version incompatible with latest dbt_utils

  #32 opened 3 years ago by rcaddell
  3

• BUG - The stg_fivetran_log__log model does now handle duplicate rows in the source logs table

  #34 opened 3 years ago by jcbmllgn
  11

• [Bug] Broken connector reported as "connected"

  #39 opened 3 years ago by carlioth
  13

• [Bug] stg_fivetran_log__log unique_combination_of_columns test is too strict

  #42 opened 3 years ago by samkessaram
  5

• [Bug] Unique combo of columns test failure due to non JSON in JSON column

  #45 opened 3 years ago by cjjohanson
  23

• BUG - Issue upgrading this package to 0.4.1 while also using dbt 0.21.0

  #26 opened 3 years ago by jcbmllgn
  5

• [Bug] Error parsing JSON in message_data in fivetran_log__connector_status

  #46 opened 3 years ago by andysteinitz
  12

• [Bug] duplicate rows in fivetran_log__schema_changelog

  #49 opened 3 years ago by CraigWilson-ZOE
  9

• [Bug] Assumes presence of optional tables

  #54 opened 3 years ago by jayhale
  4

• [Bug] Source Freshness tests still execute for sources that are distabled

  #57 opened 2 years ago by epapineau
  6

• [Duplicate Credits Spent] fivetran_log__usage_mar_destination_history dups

  #66 opened 2 years ago by lord-skinner
  3

• Macro does_table_exist causes ambiguity issue in get_relation macro

  #60 opened 2 years ago by ggmblr
  3