Pipeline ingest processor supports ignore_missing_pipeline parameter

[gaobinlong]

Description

This PR introduces a new parameter ignore_missing_pipeline for the pipeline ingest processor, when the parameter is true and the specified pipeline name doesn't exist, that processor exits quietly without throwing exception.

This enhancement can avoid indexing failures when the referenced pipeline is deleted suddenly, and can also let users create the referenced pipeline later than the current pipeline, as the example below, if the inner pipeline hasn't been created, the outer pipeline works well with setting ignore_missing_pipeline to true, sometimes users want the inner pipeline to execute at some point, when the inner pipeline is created later, it will be executed, and after it is deleted, the outer pipeline still works well:

PUT _ingest/pipeline/outer
{
  "description": "outer pipeline",
  "processors": [
    {
      "pipeline": {
        "name": "inner",
        "ignore_missing_pipeline": true
      }
    },
    {
      "set": {
        "field": "foo",
        "value": "{{bar}}"
      }
    }
  ]
}

Related Issues

#12463

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Compatibility status:

Checks if related components are compatible with change 20fffb9

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/performance-analyzer.git]

[github-actions]

❌ Gradle check result for b42da9b: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for bf9b67a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 20fffb9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[peternied]

I don't think we should take this change.

referenced pipeline is deleted suddenly

If this happens, this sounds like it should be part of application logic where the calling client should alter the pipelines associated with a request so it does not fail.

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.

[gaobinlong]

I don't think we should take this change.

referenced pipeline is deleted suddenly

If this happens, this sounds like it should be part of application logic where the calling client should alter the pipelines associated with a request so it does not fail.

Thank you, all right, this PR can hold on unless more users request for it, close this PR for now.