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 GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/08 16:21:00 UTC

[jira] [Commented] (NIFI-5500) Add array support to QueryElasticsearchHttp

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

ASF GitHub Bot commented on NIFI-5500:
--------------------------------------

GitHub user wietze opened a pull request:

    https://github.com/apache/nifi/pull/2942

    NIFI-5500

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/wietze/nifi NIFI-5500

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2942.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2942
    
----
commit 25e2ee280e0b856b73de8cd0c8f039521a883f32
Author: Wietze <wi...@...>
Date:   2018-08-08T16:17:47Z

    Adding support for array fields when outputting to attributes when using QueryElasticsearchHttp

----


> Add array support to QueryElasticsearchHttp
> -------------------------------------------
>
>                 Key: NIFI-5500
>                 URL: https://issues.apache.org/jira/browse/NIFI-5500
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.7.1
>            Reporter: Wietze B
>            Assignee: Sivaprasanna Sethuraman
>            Priority: Minor
>
> When using the QueryElasticsearchHttp processor (with output=Attributes) to query a document that contains a field with an Array rather than a String or Integer, the resulting attribute for that field will be an empty string. 
> This is due to the fact that the QueryElasticsearchHttp component doesn't handle array fields correctly. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)