[
https://issues.apache.org/jira/browse/NIFI-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618801#comment-17618801
]
Chris Sampson commented on NIFI-3262:
-------------------------------------
Think this would be a similar problem to NIFI-10067, e.g. we want to allow a
configurable way of specifying the {{IndexOperation}} part of the {{_bulk}} API
call for Records being sent to Elasticsearch.
> 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
> 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)
