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

David Handermann updated NIFI-16237:
------------------------------------
    Status: Patch Available  (was: Open)

> Correct Null Value Representation Ordering in EvaluateJsonPath
> --------------------------------------------------------------
>
>                 Key: NIFI-16237
>                 URL: https://issues.apache.org/jira/browse/NIFI-16237
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Nissim Shiman
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The extension-manifest.xml for nifi-standard-nar's EvaluateJsonPath and 
> SplitJson processor have the following: 
> {code:java}
>         <property>
>           <name>Null Value Representation</name>
>           <displayName>Null Value Representation</displayName>
>           <description>Indicates the desired representation of JSON Path 
> expressions resulting in a null value.</description>
>           <defaultValue>empty string</defaultValue>
>           <allowableValues>
>             <allowableValue>
>               <displayName>the string 'null'</displayName>
>               <value>the string 'null'</value>
>               <description/>
>             </allowableValue>
>             <allowableValue>
>               <displayName>empty string</displayName>
>               <value>empty string</value>
>               <description/>
>             </allowableValue>
>           </allowableValues>
>           ........
>           ........
>         </property>
> {code}
> The allowableValues can have their order switched. It would be prefered for 
> the order to remain the same for reproducable builds.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to