[
https://issues.apache.org/jira/browse/NIFI-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537627#comment-16537627
]
Shawn Weeks commented on NIFI-4407:
-----------------------------------
This is def a bug because if you have an attribute with a value like
TEST$$TEST and try to insert that attribute using ${attribute_name} you will
get TEST$TEST despite the attributes value being TEST$$TEST. Also
${literal('SNAP$$')} evaluates to SNAP$ as does ${literal('SNAP$$$$$$$$$')}. If
your attribute came from an external system and you try to use it as a literal
value in a later step you can't.
> Non-EL statement processed as expression language
> -------------------------------------------------
>
> Key: NIFI-4407
> URL: https://issues.apache.org/jira/browse/NIFI-4407
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.1.1, 1.0.1, 1.3.0
> Reporter: Pierre Villard
> Priority: Critical
>
> If you take a GFF with custom text: {{test$$foo}}
> The generated text will be: {{test$foo}}
> The property supports expression language and one $ is removed during the EL
> evaluation step. This can be an issue if a user wants to use a value
> containing to consecutive $$ (such as in password fields).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
