[
https://issues.apache.org/jira/browse/NIFI-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto Fowler updated NIFI-4407:
------------------------------
Comment: was deleted
(was: I don't think validateExpression or the Range are documented enough to
understand what is going on.
in the test:
{code:java}
try {
Query.validateExpression("$${attr}", false);
Assert.fail("invalid query validated");
} catch (final AttributeExpressionLanguageParsingException e) {
}
Query.validateExpression("$${attr}", true);
{code}
the bottom expression doesn't throw or fail, but that is because nothing is
ever compiled...
Can I ask why, when there is a grammar, does nifi manually validate? It is
harder when the grammar has one set of rules, then then other rules that might
be expressed in the grammar are over laid.)
> 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)
