Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Tue, 19 Sep 2017 15:18:00 +0000 (UTC)
From: "Joe Warner (JIRA)" <jira@apache.org>
To: issues@nifi.apache.org
Message-ID: <JIRA.13103263.1505834219000.147873.1505834280230@Atlassian.JIRA>
In-Reply-To: <JIRA.13103263.1505834219000@Atlassian.JIRA>
References: <JIRA.13103263.1505834219000@Atlassian.JIRA> <JIRA.13103263.1505834219802@jira-lw-us.apache.org>
Subject: [jira] [Created] (NIFI-4397) PutElasticsearchHttp Processor:
 Elasticsearch URL property isn't expanding nifi language expressions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Sep 2017 15:18:04 -0000

Joe Warner created NIFI-4397:
--------------------------------

             Summary: PutElasticsearchHttp Processor: Elasticsearch URL property isn't expanding nifi language expressions
                 Key: NIFI-4397
                 URL: https://issues.apache.org/jira/browse/NIFI-4397
             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. 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.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)