-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add limit on number of processors in Ingest pipelines #15465
Conversation
❌ Gradle check result for 290dbff: 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? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the change, Can you please add relevant UTs/ITs for the change as well?
server/src/main/java/org/opensearch/ingest/IngestPipelineValidator.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/ingest/IngestPipelineValidator.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/action/ingest/SimulatePipelineTransportAction.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/ingest/IngestPipelineValidator.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Rai <nndri@amazon.com>
Signed-off-by: Rai <nndri@amazon.com>
❌ Gradle check result for 8a39f44: 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? |
❌ Gradle check result for 99eaf02: 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? |
Signed-off-by: anand kumar rai <kumar.anand.rai@gmail.com>
Signed-off-by: Rai <nndri@amazon.com>
❌ Gradle check result for 9149544: 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? |
Created issue for flaky test - #15588 |
* Add limit on number of processors in Ingest pipelines Signed-off-by: Rai <nndri@amazon.com> (cherry picked from commit 41ba00a) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* Add limit on number of processors in Ingest pipelines (cherry picked from commit 41ba00a) Signed-off-by: Rai <nndri@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…ject#15465) * Add limit on number of processors in Ingest pipelines Signed-off-by: Rai <nndri@amazon.com>
…ject#15465) * Add limit on number of processors in Ingest pipelines Signed-off-by: Rai <nndri@amazon.com>
…ject#15465) * Add limit on number of processors in Ingest pipelines Signed-off-by: Rai <nndri@amazon.com>
…ject#15465) * Add limit on number of processors in Ingest pipelines Signed-off-by: Rai <nndri@amazon.com>
Description
Add limit on number of processors in Ingest pipelines
Related Issues
Resolves #[15464]
#15464
Check List
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.