davidrichards-etl 0.0.4 → 0.0.5
Sign up to get free protection for your applications and to get access to all the features.
- data/README.rdoc +1 -1
- data/VERSION.yml +1 -1
- metadata +1 -1
data/README.rdoc
CHANGED
@@ -101,7 +101,7 @@ If something goes wrong, you can address the issue and just restart it.
|
|
101
101
|
|
102
102
|
The original options are still stored in @etl, so you don't need to resend those. If you send them back in, they will be ignored anyway. If the problem was that you setup the options wrong, you can write something like
|
103
103
|
|
104
|
-
@etl.options[:with
|
104
|
+
@etl.options[:with] = :better_options
|
105
105
|
|
106
106
|
Because of the nature of the code, the stages that passed won't be re-run. In fact, you can take a completed etl object and call it all day long, and it will never try to restart itself. If you need it to restart, or you want to restart at an earlier stage, just do something like:
|
107
107
|
|
data/VERSION.yml
CHANGED