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

Claudiu Stanciu updated NIFI-4190:
----------------------------------
    Description: 
As a user, I would like support for Expression Language in the EvaluateXPath 
processor.

This would be a nice modification as it would allow passing of XPaths from 
attributes or content, and would permit more generic flows/templates.

As discussed in 
http://apache-nifi-developer-list.39713.n7.nabble.com/Expression-language-support-in-EvaluateXPath-td16441.html,
 ideally we want to keep the actual performances for the case when we don't use 
expression language, and we compile expressions at trigger time only where 
expression languages are used.

  was:
As a user, I would like support for Expression Language in the EvaluateXPath 
processor.

This would be a nice modification as it would allow passing of XPaths from 
attributes or content, and would permit more generic flows/templates.

As discussed in 
http://apache-nifi-developer-list.39713.n7.nabble.com/Expression-language-support-in-EvaluateXPath-td16441.html,
 ideally we want to keep the actual performances for the case where we don't 
use expression language, and we compile expressions at trigger time only where 
expression languages are used.


> Expression Language support in EvaluateXPath
> --------------------------------------------
>
>                 Key: NIFI-4190
>                 URL: https://issues.apache.org/jira/browse/NIFI-4190
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.3.0
>            Reporter: Claudiu Stanciu
>              Labels: xml
>
> As a user, I would like support for Expression Language in the EvaluateXPath 
> processor.
> This would be a nice modification as it would allow passing of XPaths from 
> attributes or content, and would permit more generic flows/templates.
> As discussed in 
> http://apache-nifi-developer-list.39713.n7.nabble.com/Expression-language-support-in-EvaluateXPath-td16441.html,
>  ideally we want to keep the actual performances for the case when we don't 
> use expression language, and we compile expressions at trigger time only 
> where expression languages are used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to