[
https://issues.apache.org/jira/browse/NIFI-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499353#comment-16499353
]
Mike Thomsen commented on NIFI-5248:
------------------------------------
In my opinion, no they cannot be updated. The problem with ElasticSearch is
that it has been very unstable in its Java API compared to Solr between v2, v5
and the roadmap beyond v5. The processor bundles didn't really take much of
that into account. The processor bundle that is unversioned in its name is
primarily for v2. There's a separate, but incomplete, bundle for v5 that uses
the transport API (which is deprecated from the client in v6 onward).
The new "restapi" processor pack focuses on client services that use the
official–and allegedly stable–new high level REST API. It can be used with V5
as a substitute for the transport API, so that means in the long run we can
just deprecate the existing bundles in favor of the new bundle once it's
feature-complete.
> Create new put processors that use the ElasticSearch client service
> -------------------------------------------------------------------
>
> Key: NIFI-5248
> URL: https://issues.apache.org/jira/browse/NIFI-5248
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
>
> Two new processors:
> * PutElasticsearchJson - put raw JSON.
> * PutElasticsearchRecord - put records.
> Both of them should support the general bulk load API and be able to do
> things like insert into multiple indexes from one payload.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
