dbt-labs / dbt-spark

dbt-spark contains all of the code enabling dbt to work with Apache Spark and Databricks
https://getdbt.com
Apache License 2.0
395 stars 221 forks source link

dbt seed truncate tables #915

Closed machov closed 11 months ago

machov commented 11 months ago

resolves https://github.com/dbt-labs/dbt-spark/issues/112

Problem

The current seed command in dbt-spark appends to existing seeded tables instead overwriting when the database is 'unmanaged' (no location specified from create schema)

Solution

Overwrite all rows from the existing seed tables and replace values.

Checklist

cla-bot[bot] commented 11 months ago

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Manrique Vargas. This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails
cla-bot[bot] commented 11 months ago

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Manrique Vargas. This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails
cla-bot[bot] commented 11 months ago

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Manrique Vargas. This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails
cla-bot[bot] commented 11 months ago

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Manrique Vargas. This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails