Github user jtstorck commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1276#discussion_r90130637
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchProcessor.java
---
@@ -74,8 +83,9 @@
Set<ValidationResult> results = new HashSet<>();
// Ensure that if username or password is set, then the other is
too
- Map<PropertyDescriptor, String> propertyMap =
validationContext.getProperties();
- if (StringUtils.isEmpty(propertyMap.get(USERNAME)) !=
StringUtils.isEmpty(propertyMap.get(PASSWORD))) {
+ String userName =
validationContext.getProperty(USERNAME).evaluateAttributeExpressions().getValue();
+ String password =
validationContext.getProperty(PASSWORD).evaluateAttributeExpressions().getValue();
--- End diff --
I don't see EL enabled in the PASSWORD PropertyDescriptor, but
evaluateAttributeExpressions() is being called on that property. Is it
intended that the PASSWORD property should allow EL?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
