+972 52-548-6969
Rhino ETLTargets
time to read 1 min | 155 words
Well, that is two items down my list already, I have added support for targets to Rhino ETL. A target is similar in concept to a target in NAnt, it specify what needs to be run when the package run. This allows to specify how we want to run the various actions that we have.
Here is a simple example:
target default:
Execute("CopyOrders") Execute("MoveCustomers")
As you can see, it just lists the pipelines that we want to run. By default, the target execute all the registered pipelines (or other actions) in parallel. But what happens when you want to run them in a sequence?
target default:
sequence:
Execute("CopyOrders")
Execute("MoveCustomers")Another option is that you have a dependency between two pipelines, but you don't care about the rest, you can do this as well, like this:
target withDependencies:
copyOrders = Execute("CopyOrders")
Execute("MoveCustomers")
Execute("AfterCopyOrders").After(copyOrders)Next task, transactions...
More posts in "Rhino ETL" series:
- (16 Oct 2007) Importing Data into MS CRM
- (13 Aug 2007) Writing to files
- (05 Aug 2007) Web Services Source
- (05 Aug 2007) Transactions
- (04 Aug 2007) Targets
- (04 Aug 2007) Aggregates
- (26 Jul 2007) Thinking about Joins & Merges
- (24 Jul 2007) First Code Drop
Comments
That looks great. I assume you can also just do
target withDependencies:
Execute("AfterCopyOrders").After(Execute("CopyOrders"))
?
What about this also as an idea...
Execute("CopyOrders").Then(Execute("AfterCopyOrders"))
or even
Execute("CopyOrders").Then("AfterCopyOrders")
Oops, overlooked your "sequence" syntax, that is very nice :-)
Comment preview