[
https://issues.apache.org/jira/browse/NIFI-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319803#comment-17319803
]
David Handermann commented on NIFI-8290:
----------------------------------------
Hi [~andrea.castello], thank you for your contribution! The code you have
contributed appears to be straightforward, and the new dependencies are
licensed under Apache Software License 2.0, which meets requirements for
inclusion.
Reviewing the implementation, however, did you attempt to interact with WURFL
service using the standard {{InvokeHTTP}} processor? Since the
WURFLDeviceEnrichProcessor passes FlowFile attributes to the service and writes
response capabilities as attributes, it seems like this could be configured
using InvokeHTTP, unless the client library does some special HTTP handling.
> Create an enrich processor that adds device detection data from WURFL
> ---------------------------------------------------------------------
>
> Key: NIFI-8290
> URL: https://issues.apache.org/jira/browse/NIFI-8290
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Andrea Castello
> Assignee: Andrea Castello
> Priority: Major
> Attachments: wurfl_processor.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Create a new processor that extracts device detection data from a WURFL
> service from a user-agent or a HTTP request.
> The mechanism and goal are similar to the ones of GeoIP enrich processor:
> enriching the data flow with new data.
>
> This processor will receive a User-Agent string or a set of HTTP request
> headers as FlowFile attributes and use them to get device detection data from
> a WURFL Microservice. These device detection data - AKA device capabilities -
> will be stored in the FlowFile as attributes with the name pattern
> "wurfl.<capability_name>"
>
> Attached image is a configuration example for the WURFL device detection
> processor
>
> Note:
> * WURFL Microservice Java client is released under Apache License 2.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)