@INROWNUM and @PARTITIONNUM
Posted: Fri Sep 28, 2007 1:04 am
We have a scenario, wherein we have 8-9 source datasets. After each dataset we have a transformer in which table_name is hardcoded. this transformer has only one column--table_name.
We are checking that if any of the dataset is having data, then that particular table_name (from transformer) is being written to the target dataset. The constraint in the transformer is '@INROWNUM=1 and @PARTITIONNUM=0'. We do have 2-node configuration file.
The problem here is, some of the datasets are working fine, but in 1-2 datasets, even if they have got data, nothing is going beyond transformer.
If anyone came across similar problem, please respond...
We are checking that if any of the dataset is having data, then that particular table_name (from transformer) is being written to the target dataset. The constraint in the transformer is '@INROWNUM=1 and @PARTITIONNUM=0'. We do have 2-node configuration file.
The problem here is, some of the datasets are working fine, but in 1-2 datasets, even if they have got data, nothing is going beyond transformer.
If anyone came across similar problem, please respond...