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/05/02 11:18:00 UTC

[jira] [Commented] (NIFI-3262) PutElasticsearch support for _routing/_parent

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

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

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

NIFI-10067: enable use of script when updating documents in Elasticsearch via PutElasticsearchJson or PutElasticsearchRecord
NIFI-3262: enable use of dynamic_templates in Elasticsearch _bulk operations

Signed-off-by: Joe Gresock <jg...@gmail.com>

This closes #6628.


> PutElasticsearch support for _routing/_parent
> ---------------------------------------------
>
>                 Key: NIFI-3262
>                 URL: https://issues.apache.org/jira/browse/NIFI-3262
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Josh Harrison
>            Assignee: Chris Sampson
>            Priority: Major
>
> Due to the structure of the current nifi Elasticsearch indexing processors, it doesn't appear possible to specify explicit _routing or _parent fields when using any of the PutElasticsearch processors (PutElasticsearch, PutElasticsearchHTTP, PutElasticsearch5).
> The ability to optionally specify the _parent and/or _routing parameters that can be present in a normal bulk index request would be really valuable.
> An alternative to adding a handled attribute would be adding support for the bulk indexing syntax as defined on https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html - a two line structure where line one contains the indexing instructions in a JSON object, and line two contains the content of the object. Each line ends with an explicit newline character (\n). This would allow bulk indexing, update, delete, etc operations to be carried out through nifi.



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