[ 
https://issues.apache.org/jira/browse/NIFI-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113096#comment-16113096
 ] 

ASF GitHub Bot commented on NIFI-4024:
--------------------------------------

Github user bbende commented on the issue:

    https://github.com/apache/nifi/pull/1961
  
    Thanks @MikeThomsen , two minor issues while testing this...
    
    1) There is a try-with-resource block that creates the RecordReader, and as 
part of that line it also creates an InputStream for the flow file, but since 
the InputStream is created inline it won't be auto-closed which can cause a 
problem later on.
    
    2) The complex field handling was only being used in the case where the 
field encoding strategy was "Bytes", which is different from how PutHBaseJson 
works.
    
    I went ahead and addressed these issues in my own branch:
    
https://github.com/bbende/nifi/commit/a9d8d038fe40b50bab1a8b59e11ad926ed07cc78
    
    If you are on-board with my changes then I'll go ahead and merge everything 
to master.
    
    Let me know.


> Create EvaluateRecordPath processor
> -----------------------------------
>
>                 Key: NIFI-4024
>                 URL: https://issues.apache.org/jira/browse/NIFI-4024
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Steve Champagne
>            Priority: Minor
>
> With the new RecordPath DSL, it would be nice if there was a processor that 
> could pull fields into attributes of the flowfile based on a RecordPath. This 
> would be similar to the EvaluateJsonPath processor that currently exists, 
> except it could be used to pull fields from arbitrary record formats. My 
> current use case for it would be pulling fields out of Avro records while 
> skipping the steps of having to convert Avro to JSON, evaluate JsonPath, and 
> then converting back to Avro. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to