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

ASF GitHub Bot commented on NIFI-1594:
--------------------------------------

Github user apiri commented on the pull request:

    https://github.com/apache/nifi/pull/255#issuecomment-213661619
  
    Hey @joaohf!  Looks like @mattyb149 has already started giving some input 
but saw that there are a few test failures concerning expression language such 
as the one below (full sample log is available at: 
https://s3.amazonaws.com/archive.travis-ci.org/jobs/114414795/log.txt).  
Haven't dug deep into the tests but wanted to call it out to your attention to 
get a fix for later incorporation.
    
    Thanks!
    
    ```
    
testPutElasticSearchOnTrigger(org.apache.nifi.processors.elasticsearch.TestPutElasticsearch)
  Time elapsed: 0.01 sec  <<< FAILURE!
    java.lang.AssertionError: java.lang.IllegalStateException: Attempting to 
retrieve value of PropertyDescriptor[Index Operation] without first evaluating 
Expressions, even though the PropertyDescriptor indicates that the Expression 
Language is Supported. If you realize that this is the case and do not want 
this error to occur, it can be disabled by calling 
TestRunner.setValidateExpressionUsage(false)
    ```


> Add option to bulk using Index or Update to PutElasticsearch
> ------------------------------------------------------------
>
>                 Key: NIFI-1594
>                 URL: https://issues.apache.org/jira/browse/NIFI-1594
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: João Henrique Ferreira de Freitas
>            Priority: Minor
>             Fix For: 0.7.0
>
>
> I have a use case where two flowfiles needs to be write using 
> PutElasticsearch. Both will write to the same document but in different 
> properties. 
> The proposal is to let the user choice if an Update operation or Index is 
> needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to