Skip to content

Commit

Permalink
Merge pull request #301 from fishtown-analytics/release/0.7.1
Browse files Browse the repository at this point in the history
Release/0.7.1
  • Loading branch information
drewbanin authored Mar 1, 2017
2 parents e874f9a + d0c3cd2 commit 80c9e9b
Show file tree
Hide file tree
Showing 5 changed files with 17 additions and 5 deletions.
2 changes: 1 addition & 1 deletion .bumpversion.cfg
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
[bumpversion]
current_version = 0.7.0
current_version = 0.7.1
commit = True
tag = True

Expand Down
8 changes: 7 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,24 @@
## dbt 0.7.1 (unreleased)
## dbt 0.7.1 (February 28, 2017)

### Overview

- [Improved graph selection](http://dbt.readthedocs.io/en/master/guide/usage/#run)
- A new home for dbt
- Snowflake improvements

#### New Features

- improved graph selection for `dbt run` and `dbt test` ([more information](http://dbt.readthedocs.io/en/master/guide/usage/#run)) ([#279](https://github.com/fishtown-analytics/dbt/pull/279))
- profiles.yml now supports Snowflake `role` as an option ([#291](https://github.com/fishtown-analytics/dbt/pull/291))

#### A new home for dbt

In v0.7.1, dbt was moved from the analyst-collective org to the fishtown-analytics org ([#300](https://github.com/fishtown-analytics/dbt/pull/300))

#### Bugfixes

- nicer error if `run-target` was not changed to `target` during upgrade to dbt>=0.7.0


## dbt 0.7.0 (February 9, 2017)

Expand Down
2 changes: 1 addition & 1 deletion dbt/version.py
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,6 @@ def is_latest():
return installed == latest


__version__ = '0.7.0'
__version__ = '0.7.1'
installed = get_version()
latest = get_latest_version()
8 changes: 7 additions & 1 deletion docs/guide/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Deploying new models frequently involves destroying prior versions of these mode

### Specifying models to run

By default, `dbt run` will execute _all_ of the models in the dependency graph. During development (and deployment), it is useful to specify only a subset of models to run. Use the `--models` flag with `dbt run` to select a subset of models to run.
By default, `dbt run` will execute _all_ of the models in the dependency graph. During development (and deployment), it is useful to specify only a subset of models to run. Use the `--models` flag with `dbt run` to select a subset of models to run. Note that the following arguments (`--models` and `--exclude`) also apply to `dbt test`!

The `--models` flag accepts one or more arguments. Each argument can be one of:
1. a package name
Expand Down Expand Up @@ -51,6 +51,12 @@ dbt run --models my_package.*+ # select all models in my_package and their
dbt run --models +some_model+ # select some_model and all parents and children
```

Finally, dbt provides an `--exclude` flag with the same semantics as `--models`. Models specified with the `--exclude` flag will be removed from the set of models selected with `--models`

```bash
dbt run --models my_package.*+ --exclude my_package.a_big_model+
```

### Run dbt non-destructively

If you provide the `--non-destructive` argument to `dbt run`, dbt will minimize the amount of destructive changes it runs against your database. Specifically, dbt
Expand Down
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
import os.path

package_name = "dbt"
package_version = "0.7.0"
package_version = "0.7.1"

setup(
name=package_name,
Expand Down

0 comments on commit 80c9e9b

Please sign in to comment.