OK, I get it ... I just add a message using the Error method of the join and then collect those errors at the end of the pipeline using GetAllErrors. What caught me was the fact, that my error would not show up in the GetAllErrors of the pipeline, but that was du to a bug. So I created a patch and submitted that to github.
Thanx for pointing me in the right direction. On 23 Jan., 21:55, Henning <[email protected]> wrote: > Thanx for the quick reply. > > Well, actually I don't want to log using log4net or similar, since I > wand to show to the user all rows that were skipped (as well as why > those rows were skipped). > > So log4net would not be sufficient. > > I will look at the return value and how to skip rows. > > Or would an inner join more appropriate? But with an inner join I > don't know about the left or right rows that didn't match up to show > them to the user, right? > > On 23 Jan., 19:05, Miles Waller <[email protected]> wrote: > > > > > > > > > Hi > > > Operations have warn, notice, info etc methods that correspond to log4net > > logging. You can log the orphan rows using them. Look at the > > withLoggingMixin class. > > > You can drop the row by not passing it via yield return and carrying on the > > enumeration of the input rows, though I think you might need to cuatomise > > the operation a bit more for that. > > > Miles > > > On 23 Jan 2011 16:47, "Henning" <[email protected]> wrote: > > > Hi, > > > I'm using rhino ETL for the first time in a project, and I'm very > > impressed by its capabilities. I use a join-operation to match two > > datasources. > > > Sometimes there might be missing data, so I override LeftOrphanRow to > > "log" the error. So I though I would throw an exception and then at > > the end of the process collect all occured exceptions using > > GetAllErrors(). > > > But as it seems the process is being aborted with the first exception. > > Is that intentionally? What would be the best way to deal with > > OrphanRows? > > > -- > > 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]<rhino-tools-dev%2Bunsubscribe@ > > googlegroups.com> > > . > > For more options, visit this group > > athttp://groups.google.com/group/rhino-tools-dev?hl=en. -- 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.
