Reject record number cut off
Posted: Mon Jan 23, 2012 4:29 pm
My jobs may reject records in various stages, but I would like to log only a specific number (project wide parameter X) of rejected records and disregard the rest.
I have a shared container that I send all the reject to. The container logs the rejects into the database tables. I'm only interested in the first X records, but any of the rejected records will do.
I tried using @inrownum and having record number column in the transformer, but this solution does not work with parallel processing, as it counts records on each node separately.
Providing that following a transformer stage I also have an aggregator in this container (I need to abort if the number of rejects goes above a certain threshold, specific to each job) can I run the transformer in the sequential mode to use @inrownum without a detrimental effect on the performance?
I have a shared container that I send all the reject to. The container logs the rejects into the database tables. I'm only interested in the first X records, but any of the rejected records will do.
I tried using @inrownum and having record number column in the transformer, but this solution does not work with parallel processing, as it counts records on each node separately.
Providing that following a transformer stage I also have an aggregator in this container (I need to abort if the number of rejects goes above a certain threshold, specific to each job) can I run the transformer in the sequential mode to use @inrownum without a detrimental effect on the performance?