You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2019/07/10 16:55:01 UTC

[jira] [Resolved] (NIFI-6320) ExtractHL7Attributes should better tolerate custom segments (e.g. Z segments)

     [ https://issues.apache.org/jira/browse/NIFI-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt resolved NIFI-6320.
-------------------------------
    Resolution: Fixed

> ExtractHL7Attributes should better tolerate custom segments (e.g. Z segments)
> -----------------------------------------------------------------------------
>
>                 Key: NIFI-6320
>                 URL: https://issues.apache.org/jira/browse/NIFI-6320
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.9.2
>         Environment: OSX iMac 
>            Reporter: Gary Teichrow
>            Priority: Minor
>              Labels: Processor, hl7
>             Fix For: 1.10.0
>
>   Original Estimate: 1h
>          Time Spent: 20m
>  Remaining Estimate: 40m
>
> If a user is processing an HL7 message that contains custom segments (e.g. Z segments), an NPE is thrown at line 288 in ExtractHL7Attributes.java upon encountering that segment. The call to segment.getNames() will return a list of Nulls from HAPI for this custom segment.
> Added a check whereby, if the user is using the "Use Segment Names" option in the ExtractHL7Attributes processor and the HL7 message being processed contains custom user segments (e.g., Z Segments), the code will downgrade to returning the Segment Label as it does when this option is not used. Without this a null pointer is thrown at line 288.



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