[
https://issues.apache.org/jira/browse/NIFI-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624716#comment-14624716
]
ASF GitHub Bot commented on NIFI-751:
-------------------------------------
Github user jackowaya commented on the pull request:
https://github.com/apache/incubator-nifi/pull/70#issuecomment-120950010
Made many changes here, including I believe all of Joe's suggestions and
the majority of Ryan's. A few little notes:
* I wound up using Scanner to do the text parsing. I figured Scanner
probably knows better how to parse numbers than I do. However, that does mean
that text like "123 Fake Street" will convert to int which is a little
questionable. Should be easy to write up a full-regex version if we decide we
want that.
* The code for sending just the failed records down the error relationship
got a little nasty. It calls session.write on a copy of the incoming flowfile,
then completely ignores that flowfile and uses the failed records it collected
during the first pass through the input data.
> Add Processor To Convert Avro Formats
> -------------------------------------
>
> Key: NIFI-751
> URL: https://issues.apache.org/jira/browse/NIFI-751
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.1.0
> Reporter: Alan Jackoway
>
> When working with data from external sources, such as complex WSDL, I
> frequently wind up with complex nested data that is difficult to work with
> even when converted to Avro format. Specifically, I often have two needs:
> * Converting types of data, usually from string to long, double, etc. when
> APIs give only string data back.
> * Flattening data by taking fields out of nested records and putting them on
> the top level of the Avro file.
> Unfortunately the Kite JSONToAvro processor only supports exact conversions
> from JSON to a matching Avro schema and will not do data transformations of
> this type. Proposed processor to come.
> Discussed this with [~rdblue], so tagging him here as I don't have permission
> to set a CC for some reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
