I'm digging more into ETL and I have come across
NestedLoopsJoinOperation and JoinOperation. I cannot tell what the
difference is, or why I would use one over the other? Also, why are
the rows ignored rather than passed to the let and right operations?

I'm also trying to understand the PartialEtlProcess. Is the idea of
Partial to load multiple subset? Like if I wanted to branch my
operations with each branch containing multiple processes?
Register(new GetData())
.Register(new BranchingOperation()
        .Add(Partial
                      .Register(OperationA)
                      .Register(OperationB))
        .Add(Partial
                      .Register(OperationC)
                      .Register(OperationD))
);

In this scenario the operations would run:
[Branch 1] A1, B1, A2, B2
[Branch 2] C1, D1, C2, D2
where A & C would be intermediate logical operations (transformations)
and B & D are output operations?

Trying to follow thread 
http://groups.google.com/group/rhino-tools-dev/browse_thread/thread/e13f23611d5c7eda,
why isn't it possible to join after a branch? Is this because the left
and right operations are passed null?

here is what I have
a single flat DBF file. I need to import this into a Sql Database. Sql
has 2 tables Parent 1-N Children 1-N GrandChildren
when the data is imported I need to preform 3 different operations:
1. group the source by field
2. insert new groups into Parent
3. insert children & grand children in DBF that are not in SQL (left
join)
4. update existing children and grand children (inner join, there will
always be the same number of grand children)
5. delete Parents from SQL that do not have any children

Operation 1 only applies to operation 2, so I figure this could be a
branch.
Operations 3 and 4 can also be done independently of one another,
again branching.
Operations 3 and 4 are dependent on the completion of operation 2.
Operation 5 must be executed after 3 and 4 are complete.

It looks like Operations 3 & 4 are actually 2 output command. in which
case I must break this logic into two operations and branch together.

I would like this to occur within a single transaction/ETL process,
but I'm not sure if that's possible, or reasonable?
-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.


Reply via email to