ASN1Parse emits less tuples than expected
This can happen if input data does not conform to the grammar.
Symptoms
The nTuplesSent metric shows lower values than the nRecordsDecoded metric. You also see less tuples in the output than expected, for example if you know the number of records in the input data. To diagnose the problem use the getErrors() custom output function on the statistics port. You will see errors indicating that a constraint failed, similar to this:
record=4,message="Some-Field: constraint failed (src/operator/Test1/ParsedRecords/Some-Field.c:31)"
This output also contains the record number and the name of the ASN.1 field with the constraint. Use this information to find and verify the input data that does not conform to the grammar.
Causes
Eihter the grammar is not correct or the data source emits erroneous data. The ASN.1 grammar can contain constraints on data structures. For example an OCTET STRING may be limited to contain exactly 5 octets. If the octet string in the input data contains 4 or 6 bytes, it does not conform to the grammar. With default settings, the ASN1Parse operator will reject the data structure containing this octet string.
Resolving the problem
The preferred option should be to fix the data source or the incorrect grammar. Another option is, to configure the parser to ignore constraint violations in the input data. To do so set the following operator parameter :
checkConstraints : false;