Add support for filtering rows in a delimited file (wish list) about beanio HOT 8 CLOSED

This is somewhat already supported.  Any matched records (identified by fields 
where rid="true") that are not explicitly bound to a class are skipped.

However, the fact that you must declare record mappings for ignored records is 
cumbersome (but still recommended if you are at all worried about the integrity 
of the file).  It is also difficult to match records based on a field that does 
NOT match a particular regex pattern or literal.  So there are two things I'm 
going to look into:

1.  A stream level setting for ignoring unmatched records.
2.  A field level setting to "inverse" the matched literal or regex pattern, 
something like not="true".

And one point of clarification, filtering unmarshalled objects as opposed to 
records does NOT increase memory requirements assuming you are processing the 
file one record at a time (which is recommended for large files).  A better 
argument would be an increase in CPU utilization, although probably not 
substantial.

Maybe you can expose an API for marshalling/unmarshlling to call a user-defined 
callback.  This way, filtering can be implemented, or encryption/decryption, or 
other processing.

Proceeding with functionality to ignore unidentified records for 2.0.4.

@cw10025 - Your request is kind of vague.  Could you provide a sample callback 
interface that you would like to see if you're still interested?

Thanks Kevin; we got it working by:
  * Setting the Camel BeanIO Data Format to setUnexpectedRecords(true);
  * Suppressing the SLF4J WARN logs for the BeanIODataFormat class.

Looking forward to 2.0.4 where we'll potentially be able to remove those 
workarounds.

I've upgraded to beanio 2.0.4 but am still seeing the WARN level messages. e.g.:

[main] WARN org.apache.camel.dataformat.beanio.BeanIODataFormat - BeanIO: 
Unexpected record 'header' at line 56642: 498108      Alt Code        ABCDEFG

Please consider reopening this issue. Thanks.

Can you provide a mapping file and sample input that reproduces the issue?  
Note that an unexpected record exception is typically a record out of order and 
is not the same thing as an unidentified record.

Thanks,
Kevin