Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 654A4200D15 for ; Thu, 21 Sep 2017 04:47:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 644271609E4; Thu, 21 Sep 2017 02:47:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AB5611609E2 for ; Thu, 21 Sep 2017 04:47:05 +0200 (CEST) Received: (qmail 11379 invoked by uid 500); 21 Sep 2017 02:47:04 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 11364 invoked by uid 99); 21 Sep 2017 02:47:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Sep 2017 02:47:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F3B1318B968 for ; Thu, 21 Sep 2017 02:47:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id c1VM4d3OOt28 for ; Thu, 21 Sep 2017 02:47:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CF254610E2 for ; Thu, 21 Sep 2017 02:47:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9DA07E0D4E for ; Thu, 21 Sep 2017 02:47:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7C3F121907 for ; Thu, 21 Sep 2017 02:47:00 +0000 (UTC) Date: Thu, 21 Sep 2017 02:47:00 +0000 (UTC) From: "Joseph Percivall (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-4396) PutElasticsearchHttp Processor: Type property isn't expanding nifi language expressions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 21 Sep 2017 02:47:06 -0000 [ https://issues.apache.org/jira/browse/NIFI-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174156#comment-16174156 ] Joseph Percivall commented on NIFI-4396: ---------------------------------------- Hello [~JoeWarner], can you elaborate a bit on what you mean by "expanding" the Nifi expressions and why you believe it's not working? Looking at the source for PutElasticsearchHttp 1.3.0, we do the call to evaluate the type here[1], the property supports expression language (as stated here[2]) and the validator handles it here[3]. [1] https://github.com/apache/nifi/blob/4e4d14f86ff21d2c7d20d9e180acee54a2ddf93b/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearchHttp.java#L244 [2] https://github.com/apache/nifi/blob/4e4d14f86ff21d2c7d20d9e180acee54a2ddf93b/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearchHttp.java#L106 [3] https://github.com/apache/nifi/blob/4e4d14f86ff21d2c7d20d9e180acee54a2ddf93b/nifi-commons/nifi-utils/src/main/java/org/apache/nifi/processor/util/StandardValidators.java#L170 > PutElasticsearchHttp Processor: Type property isn't expanding nifi language expressions > --------------------------------------------------------------------------------------- > > Key: NIFI-4396 > URL: https://issues.apache.org/jira/browse/NIFI-4396 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.3.0 > Reporter: Joe Warner > Priority: Minor > > Despite the documentation saying that the PutElasticsearchHttp processor should support expression language this isn't happening. The Index property works correctly however. Looking the source I notice that these two properties use different validators and wonder if the issue could be related. > Technically I guess this isn't a 'major' issue, but it is quite painful to use it without the replacement happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)