You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Sargrad (JIRA)" <ji...@apache.org> on 2019/04/24 21:02:00 UTC

[jira] [Commented] (NIFI-6241) ConvertRecord Schema Inference fails to infer complete schema

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

David Sargrad commented on NIFI-6241:
-------------------------------------

I've added a script that allows one to reproduce this problem easily.[^Reproduce_ConvertRecord_Shortcoming.xml]

> ConvertRecord Schema Inference fails to infer complete schema
> -------------------------------------------------------------
>
>                 Key: NIFI-6241
>                 URL: https://issues.apache.org/jira/browse/NIFI-6241
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.9.2
>            Reporter: David Sargrad
>            Priority: Major
>         Attachments: Reproduce_ConvertRecord_Shortcoming.xml, image-2019-04-24-13-38-16-605.png, image-2019-04-24-13-39-36-327.png, image-2019-04-24-13-41-00-704.png, image-2019-04-24-13-41-26-860.png, image-2019-04-24-13-43-28-531.png, image-2019-04-24-13-43-59-706.png
>
>
> I've got a simple test flow as depicted below:
>  
>  
> !image-2019-04-24-13-38-16-605.png!
>  
> The input XML is:
> !image-2019-04-24-13-41-26-860.png!
>  
> The output JSON is almost correct, yet it is missing two critical fields (they both show up as "null". The null fields are {color:#ff0000}position{color} and {color:#ff0000}ncsmTrackData{color}.
>  
> !image-2019-04-24-13-41-00-704.png!
>  
> The configuration of my ConvertRecord is:
> !image-2019-04-24-13-43-28-531.png!
>  
> My XMLReader configuration is:
> !image-2019-04-24-13-43-59-706.png!
>  
>  Questions:
>  # Why are these two fields null? 
>  # Why are all the fltdMessage attributes being ignored?
> It would seem that this is a bug, or at least a major shortcoming, in the schema inference capability. If there were a way for me to view the inferred schema, then I could use that as a starting point. However its not clear from the documentation how to view that schema.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)