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

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

Commit 2e1f276f063d6309ddba830ae224c7840dae0f64 in nifi's branch 
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2e1f276 ]

NIFI-8790 allow Expression Language for Index Operation in 
PutElasticsearchRecord

Improved validation for PutElasticsearchRecord Index Operation property

Signed-off-by: Matthew Burgess <[email protected]>

This closes #5220


> PutElasticsearchRecord incorrectly validates Index Operation for Expression 
> Language input
> ------------------------------------------------------------------------------------------
>
>                 Key: NIFI-8790
>                 URL: https://issues.apache.org/jira/browse/NIFI-8790
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.13.0
>            Reporter: Chris Sampson
>            Assignee: Chris Sampson
>            Priority: Minor
>             Fix For: 1.15.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> {{Index Operation}} property was added to PutElasticsearchRecord as part of 
> NIFI-7474. IT accepts Expression Language (FlowFile Attributes) *but also* 
> specifes a list of allowed values - this means that use of Expression 
> Language can never be valid for the property.
> A different validation should be used if Expression Language is to be allowed 
> such that the processor accepts Expression Language (and later checks it's a 
> valid operation type after evaluating the expression against the invoming 
> FlowFile) *or* the value is one of the allowed operations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to