Matt Burgess created NIFI-1576:
----------------------------------
Summary: Incorporate feedback/improvements to Elasticsearch
processors
Key: NIFI-1576
URL: https://issues.apache.org/jira/browse/NIFI-1576
Project: Apache NiFi
Issue Type: Improvement
Reporter: Matt Burgess
Since the release of Apache NiFi 0.5.0 containing FetchElasticsearch and
PutElasticsearch processors, there have been some improvements identified that
would add to the usability, flexibility, and power of the Elasticsearch
processor(s). This Jira should capture those improvements for incorporation in
a future release.
Three initial observations:
1) FetchElasticsearch currently requires input, but it is possible to configure
the processor such that no information is required from an incoming flow file.
The processor should be changed to allow (but not require) input.
2) FetchElasticsearch specifies a "Document Identifier" property which may or
may not contain Expression Language to determine the document ID for fetching.
However PutElasticsearch only works when the IDs are unique, so it specifies a
"Identifier Attribute" which forces the user to point at an existing attribute.
The documentation should be very clear about what the properties are and
why/how they're used.
3) Related to #2, PutElasticsearch's "Identifier Attribute" is required and a
value for that attribute is currently required. Instead, if no value is
present, the processor should leverage the auto-generated ID feature of the
Elasticsearch API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
