You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/04/26 16:58:00 UTC

[jira] [Commented] (NIFI-11483) JsonQueryElasticsearch based processor properties incorrectly using AllowableValue value instead of displayName

    [ https://issues.apache.org/jira/browse/NIFI-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716821#comment-17716821 ] 

ASF subversion and git services commented on NIFI-11483:
--------------------------------------------------------

Commit 99b2412ad4ad3af72bff189404f6d817417660b8 in nifi's branch refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=99b2412ad4 ]

NIFI-11483 Correctly use DescribedValue for JsonQueryElasticsearch

This closes #7195

Signed-off-by: David Handermann <ex...@apache.org>


> JsonQueryElasticsearch based processor properties incorrectly using AllowableValue value instead of displayName
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-11483
>                 URL: https://issues.apache.org/jira/browse/NIFI-11483
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.21.0
>            Reporter: Chris Sampson
>            Assignee: Chris Sampson
>            Priority: Minor
>             Fix For: 1.latest, 2.latest
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The {{JsonQueryElasticsearch}} (and extending processors) are incorrectly using the {{AllowableValue}}'s {{getValue}} instead of {{getDisplayName}} for the Result Hit/Aggregation properties.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)