You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Raymond (JIRA)" <ji...@apache.org> on 2019/07/29 06:45:00 UTC

[jira] [Commented] (NIFI-4190) Expression Language support in EvaluateXPath

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

Raymond commented on NIFI-4190:
-------------------------------

I agree with Claudiu. There are the following functions:

escapeJson
escapeXml

unescapeJson
unescapeXml

However for searching there is only jsonPath and no xpath (xml). Especially for routing this would be practical instead of using evaluateXpath first.

 

 

> 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
>            Priority: Major
>              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
(v7.6.14#76016)