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

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

GitHub user mattyb149 opened a pull request:

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

    NIFI-5266: Sanitize ES parameters in PutElasticsearchHttp processors

    I ran the PutESHttp integration tests as well (after adding new ones to 
test this behavior). Also fixed a couple of minor issues while I was in here, 
such as adding unit tests around Expression Language for the ES URL, fixing the 
result/reason error handling to return the right string, etc.
    
    ### 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)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] 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/mattyb149/nifi NIFI-5266

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

    https://github.com/apache/nifi/pull/2760.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 #2760
    
----
commit 5e5cc7e00092893c762e859a4b2ba305446347e7
Author: Matthew Burgess <mattyb149@...>
Date:   2018-06-04T21:04:01Z

    NIFI-5266: Sanitize ES parameters in PutElasticsearchHttp processors

----


> PutElasticsearchHttp processors should sanitize parameters
> ----------------------------------------------------------
>
>                 Key: NIFI-5266
>                 URL: https://issues.apache.org/jira/browse/NIFI-5266
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>
> Currently PutElasticsearchHttp and PutElasticsearchHttpRecord put the 
> property values for index, type, and id into the Bulk API command as they are 
> specified in the processor properties. This can cause errors when special 
> characters such as a double-quote (") is encountered. Although a double-quote 
> (for example) is not supported in an index name, it is valid in a type name 
> and should be allowed.



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

Reply via email to