Adam Turley created NIFI-16028:
----------------------------------
Summary: PutElasticsearchJson: support nested field paths for
Index, Identifier, and Timestamp fields
Key: NIFI-16028
URL: https://issues.apache.org/jira/browse/NIFI-16028
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: Adam Turley
Fix For: 2.10.0
The PutElasticsearchJson processor can extract the Elasticsearch index name,
document ID, and @timestamp value from a field within each document (via the
Index Field, Identifier Field, and Timestamp Field properties added in
NIFI-15985). Today those properties only match a top-level field name, so a
document that carries this information in a nested object cannot be used as a
source. For example, with a document like: \{ "@metadata": { "index":
"logs-2026", "id": "abc-123" }, "message": "..." } setting Index Field to
"@metadata/index" currently finds nothing (there is no top-level key literally
named "@metadata/index") and silently falls back to the configured Index
property. Nesting routing/metadata under an envelope such as "@metadata" is a
common pattern (e.g. coming from Logstash), so users have no way to get the
index/id/timestamp from it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
