add initial MLInferenceSearchResponseProcessor

[mingshl]

Description

add initial MLInferenceSearchResponseProcessor

this PR only support collecting many document field in a list to add in one prediction call.

The one document to one prediction call will add incrementally in a next PR

Issues Resolved

#2173
#2444

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

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.

[jngz-es]

Why do we pass both response and hits? I think response already includes hits.

[mingshl]

I need the response here when there is any failure in rewrite, it directly returns the original response

[jngz-es]

So remove hits? The response has hits.

[mingshl]

removed!

[jngz-es]

Check if hits is null first? According to my below comment, maybe
if (response.getHits().getHits() == null || response.getHits().getHits().length == 0),
then
rewriteResponseDocuments(response, responseListener) ?

[mingshl]

when the hits is null but not empty, it should throw exception and we catch it by ignoreFailure flag, if ignoreFailure is false, it will throw exception accordingly. A valid search response with not matching any document is like this

An empty hit when hits.length == 0, we skip processing the ml inference here.

{
  "took": 45,
  "timed_out": false,
  "_shards": {
    "total": 404,
    "successful": 404,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 0,
      "relation": "eq"
    },
    "max_score": null,
    "hits": []
  }
}

[dhrubo-os]

if ignoreFailure is false, it will throw exception accordingly.

So in this case we will show "Null pointer exception" to the customer? Does this sound reasonable to customer to get a null pointer exception and having no clue what exactly happened?

[mingshl]

resolved merge conflict

[mingshl]

All Build and Test CI passed. can you please approve again? @b4sjoo @Zhangxunmt

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2688-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 01084b4a014e1cd355cee3d4f45a986b5001681f
# Push it to GitHub
git push --set-upstream origin backport/backport-2688-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-2688-to-2.x.

[opensearch-trigger-bot]

The backport to 2.16 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.16 2.16
# Navigate to the new working tree
cd .worktrees/backport-2.16
# Create a new branch
git switch --create backport/backport-2688-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 01084b4a014e1cd355cee3d4f45a986b5001681f
# Push it to GitHub
git push --set-upstream origin backport/backport-2688-to-2.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.16

Then, create a pull request where the base branch is 2.16 and the compare/head branch is backport/backport-2688-to-2.16.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2688-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 01084b4a014e1cd355cee3d4f45a986b5001681f
# Push it to GitHub
git push --set-upstream origin backport/backport-2688-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-2688-to-2.x.