Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Cannot Reproduce
-
1.3.0
-
None
-
None
Description
Despite the documentation saying that the PutElasticsearchHttp processor should support expression language this isn't happening. The Index property works correctly however. The property validates whether the value looks like a URL. But it seems like this validation is taking place before the expression is evaluated. Also, expressions like 'http://${url}' still are not evaluated.
Technically I guess this isn't a 'major' issue, but it is quite painful to use it without the replacement happening. See also NIFI-4396 which is very similar behaviour.