Skip to content

NIFI-16247 - Add ingest pipeline support to PutElasticsearchJson - #11589

Open
agturley wants to merge 1 commit into
apache:mainfrom
agturley:NIFI-16247
Open

NIFI-16247 - Add ingest pipeline support to PutElasticsearchJson#11589
agturley wants to merge 1 commit into
apache:mainfrom
agturley:NIFI-16247

Conversation

@agturley

Copy link
Copy Markdown
Contributor

Add Pipeline, Pipeline Field, and Retain Pipeline Field properties, mirroring the existing Index configuration. Pipeline sets a static ingest pipeline for every document, while Pipeline Field resolves the pipeline per document from the payload and honors the Field Path Mode property, so the value can come from a top-level field or a nested "/"-delimited path. When the field is absent or the property is blank, the static Pipeline value is used as the fallback.

The resolved value is written to the bulk action header for Index and Create operations, so records within a single FlowFile can be routed through different ingest pipelines in one _bulk request. Retain Pipeline Field controls whether the field is stripped from the document body before indexing; the field is stripped whenever requested, including for operations the pipeline itself does not apply to, so routing metadata is never indexed.

Generalize the index name extraction helpers to resolveFieldValue and extractFieldValue since they are now shared with the pipeline resolution.

Summary

NIFI-16247

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
  • Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • [X ] Build completed using ./mvnw clean install -P contrib-check
    • [X ] JDK 21
    • JDK 25

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

Add Pipeline, Pipeline Field, and Retain Pipeline Field properties, mirroring
the existing Index configuration. Pipeline sets a static ingest pipeline for
every document, while Pipeline Field resolves the pipeline per document from
the payload and honors the Field Path Mode property, so the value can come
from a top-level field or a nested "/"-delimited path. When the field is
absent or the property is blank, the static Pipeline value is used as the
fallback.

The resolved value is written to the bulk action header for Index and Create
operations, so records within a single FlowFile can be routed through
different ingest pipelines in one _bulk request. Retain Pipeline Field
controls whether the field is stripped from the document body before
indexing; the field is stripped whenever requested, including for operations
the pipeline itself does not apply to, so routing metadata is never indexed.

Generalize the index name extraction helpers to resolveFieldValue and
extractFieldValue since they are now shared with the pipeline resolution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant