|
Viewing Issue Advanced Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0011288 |
[TIS Studio] Java components |
feature |
N/A |
2010-01-25 12:55 |
2010-08-17 22:10 |
|
|
Reporter |
alevy |
View Status |
public |
|
|
Assigned To |
mhirt |
|
Priority |
normal |
Resolution |
duplicate |
Platform |
|
|
Status |
closed |
|
OS |
|
|
Projection |
none |
|
OS Version |
|
|
ETA |
none |
Fixed in Version |
|
Product Version |
3.2.3 |
| |
Target Version |
|
Product Build |
|
|
|
Summary |
0011288: Rejection of all records with duplicated keys |
|
Description |
I would like an option in tUniqueRow (or a new component) to separate out ALL records with a duplicated key to a rejects flow (in contrast to the current approach which lets through the first record with a given key and only rejects subsequent records with the same key).
I actually think that logically this should (already) be part of tSchemaComplianceCheck, at least as an option. However, two reasons for having it in tUniqueRow instead are that:
1. I presume including a duplicate key check would fundamentally change the nature of tSchemaComplianceCheck by preventing it from doing through-flow processing; and
2. Having the duplicate key check separate from tSchemaComplianceCheck allows the user to decide if they want the duplicate key check performed before or after the other validations i.e. if there were two records with the same key but one would be rejected for other reasons, whether the other should still be rejected as a duplicate key. |
|
Steps To Reproduce |
|
|
Additional Information |
|
| Tags |
No tags attached. |
|
|
generated language |
java |
|
workload (in half days) |
|
|
|
Attached Files |
|
|
|
Relationships 
(0053802)
