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

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/21 21:04:00 UTC

[jira] [Commented] (NIFI-10106) Fix potential NPE in LookupRecord

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

ASF subversion and git services commented on NIFI-10106:
--------------------------------------------------------

Commit c08996515bbf76253563e6f050b32dd8549919e7 in nifi's branch refs/heads/main from tpalfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c08996515b ]

NIFI-10106 Avoid NPE in LookupRecord.createLookupCoordinates (#6111)



> Fix potential NPE in LookupRecord
> ---------------------------------
>
>                 Key: NIFI-10106
>                 URL: https://issues.apache.org/jira/browse/NIFI-10106
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Tamas Palfy
>            Assignee: Tamas Palfy
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> _LookupRecord_ can throw a _NullPointerException_ during _createLookupCoordinates_ when one of the record path evaluation results in a FieldValue that has no RecordField.
> This can occur for example when a dynamic property is set that evaluates to a LiteralValuePath, like a _toString_ [RecordPath Domain-Specific Language (DSL)|https://localhost:18443/nifi-docs/html/record-path-guide.html] call.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)