Skip to content

Commit 80c9e9b

Browse files
authored
Merge pull request #301 from fishtown-analytics/release/0.7.1
Release/0.7.1
2 parents e874f9a + d0c3cd2 commit 80c9e9b

File tree

5 files changed

+17
-5
lines changed

5 files changed

+17
-5
lines changed

.bumpversion.cfg

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
[bumpversion]
2-
current_version = 0.7.0
2+
current_version = 0.7.1
33
commit = True
44
tag = True
55

CHANGELOG.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,24 @@
1-
## dbt 0.7.1 (unreleased)
1+
## dbt 0.7.1 (February 28, 2017)
22

33
### Overview
44

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

89
#### New Features
910

11+
- 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))
1012
- profiles.yml now supports Snowflake `role` as an option ([#291](https://github.com/fishtown-analytics/dbt/pull/291))
1113

1214
#### A new home for dbt
1315

1416
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))
1517

18+
#### Bugfixes
19+
20+
- nicer error if `run-target` was not changed to `target` during upgrade to dbt>=0.7.0
21+
1622

1723
## dbt 0.7.0 (February 9, 2017)
1824

dbt/version.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,6 @@ def is_latest():
6767
return installed == latest
6868

6969

70-
__version__ = '0.7.0'
70+
__version__ = '0.7.1'
7171
installed = get_version()
7272
latest = get_latest_version()

docs/guide/usage.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Deploying new models frequently involves destroying prior versions of these mode
1717

1818
### Specifying models to run
1919

20-
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.
20+
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`!
2121

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

54+
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`
55+
56+
```bash
57+
dbt run --models my_package.*+ --exclude my_package.a_big_model+
58+
```
59+
5460
### Run dbt non-destructively
5561

5662
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

setup.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
import os.path
44

55
package_name = "dbt"
6-
package_version = "0.7.0"
6+
package_version = "0.7.1"
77

88
setup(
99
name=package_name,

0 commit comments

Comments
 (0)