search

dbt-msft / tsql-utils

dbt-utils for the dbt-msft family of packages
MIT License
26 stars 27 forks source link

Bump dbt-synapse from 1.2.0 to 1.3.2 #91

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 1 year ago

Bumps dbt-synapse from 1.2.0 to 1.3.2.

Release notes

Sourced from dbt-synapse's releases.

v1.3.2

What's Changed

v1.3.2

Make sure to read the changelog for dbt-synapse 1.3.2.

Full Changelog: https://github.com/dbt-msft/dbt-synapse/compare/v1.3.0...v1.3.2

v1.3.0

What's Changed

v1.3.0

Make sure to read the changelog for dbt-sqlserver 1.3.0.

Full Changelog: https://github.com/dbt-msft/dbt-synapse/compare/v1.2.0...v1.3.0

v1.3.0b1

v1.3.0

Make sure to read the changelog for dbt-sqlserver 1.3.0.

Features

  • Official compatibility with dbt-core 1.3.0. Python models are not supported in this version.

Full Changelog: https://github.com/dbt-msft/dbt-synapse/compare/v1.2.0...v1.3.0b1

Changelog

Sourced from dbt-synapse's changelog.

v1.3.2

You can now create seed tables with different distribution and index strategy by providing required confiuration in dbt_project.yml file #76. The default choice is REPLICATE disttribution and HEAP (no indexing). If you want to override this configuration, the following sample should help.

seeds:
  jaffle_shop:
    index: HEAP
    dist: ROUND_ROBIN
    raw_customers:
      index: HEAP
      dist: REPLICATE
    raw_payments:
      dist: HASH(payment_method)
      index: CLUSTERED INDEX(id,order_id)

Create a new context "seeds:" at the root followed by project name and seed name. In this case the project name is jaffle_shop and seeds are raw_customers and raw_payments. Provide index and distribution values using index and dist keys. Use replicate, round_robin, hash({column name}) as a value. Example: dist: replicate. The raw_customers seed table will be replicated a table. For hash distribution, the user need to provide the vaule HASH(payment_method). Example: dist: hash(payment_method)

To specific index, index as a key and CLUSTERED INDEX({Column1, Column2}), HEAP, CLUSTERED COLUMNSTORE INDEX as a value. Example: index: HEAP. The raw_customers seed table will use heap index strategy. For clustered index, the user need to provide one or more columns to create clustered index on. Example: index: CLUSTERED INDEX(id,order_id). The default value of index and distribution can also be set for all seeds under project name.

Note Multi-column distribution is not supported in this release for seed tables.

v1.3.1

Integer seed value set to 0 is ingested as a NULL. Bug fix to handle integer seed value when set to 0. #136.

v1.3.0

Make sure to read the changelog for dbt-sqlserver 1.3.0.

Features

  • Official compatibility with dbt-core 1.3.0. Python models are not supported in this version.
Commits
  • 173cc0b Merge pull request #138 from dbt-msft/prdpsvs/issue76
  • ac6b7a4 Updated config for seed tables in helper materialization.
  • 63a6557 deleted str_lower.sql file
  • 0a307dc Linked v1.3.2 to issue 76 in change log
  • 15e3c2a Updated version file
  • dca5a4c Update to the changelog
  • e5ab902 Updated changelog to reflect changes related to seed tables dist and index st...
  • 4331d8d Added a function to create table in synapse with distribution and index. Adde...
  • 51b1a98 Merge pull request #136 from dbt-msft/prdpsvs/learn
  • 358c563 Updating the version to 1.3.1
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.