nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pvillard31 <>
Subject [GitHub] nifi issue #858: NIFI-1971 - Introduce QueryWhois processor
Date Mon, 12 Sep 2016 10:25:32 GMT
Github user pvillard31 commented on the issue:
    Hey @trixpan 
    Few remarks, regarding the ``customValidate``, I'd suggest the following example:
                results.add(new ValidationResult.Builder()
                        .explanation("NONE parser does not support batching. Configure Batch
Size to 1 or use another parser.")
    This way instead of:
    '' validated against 'QUERY_PARSER' is invalid because NONE parser...
    I have:
    '500' validated against 'Results Parser' is invalid because NONE parser...
    Also, when I set the following configuration:
    <img width="759" alt="screen shot 2016-09-12 at 12 20 24 pm" src="">
    I have the following result:
    Standard FlowFile Attributes
    Key: 'entryDate'
    	Value: 'Mon Sep 12 12:14:31 CEST 2016'
    Key: 'lineageStartDate'
    	Value: 'Mon Sep 12 12:14:31 CEST 2016'
    Key: 'fileSize'
    	Value: '0'
    FlowFile Attribute Map Content
    Key: 'enrich.whois.record0.group0'
    	Value: 'Request must be in the form of 'origin a.b.c.d' or 'peer a.b.c.d' where a.b.c.d
is a valid IPv4 address.
    Key: 'filename'
    	Value: '2616257872984957'
    Key: 'path'
    	Value: './'
    Key: 'src.ip'
    	Value: ''
    Key: 'uuid'
    	Value: '0bc829ab-3423-4f8d-bed3-dd3c8ee7db23'
    Is that expected? I'd assume (with the processor configuration) that the result is not
parsed in the same way but that the request is still performed correctly, no?
    Will continue reviewing later today.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message