#709 Return empty response for empty mappings and no applied aliases

[goyamegh]

Description

Returns an empty response instead of exception in case of:

1. empty index mappings are present,
2. no applied aliases are present on the index

Issues Resolved

#709

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.

[eirsep]

plz add rest tests for both the scenarios

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (24e94b4) 24.81% compared to head (6ad9519) 24.74%.
Report is 7 commits behind head on main.

❗ Current head 6ad9519 differs from pull request most recent head d8bcecb. Consider uploading reports for the commit d8bcecb to get more accurate results

Files	Patch %	Lines
...ch/securityanalytics/mapper/MappingsTraverser.java	75.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #724      +/-   ##
============================================
- Coverage     24.81%   24.74%   -0.08%     
  Complexity     1021     1021              
============================================
  Files           275      275              
  Lines         12670    12663       -7     
  Branches       1390     1389       -1     
============================================
- Hits           3144     3133      -11     
- Misses         9258     9264       +6     
+ Partials        268      266       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[eirsep]

fix dco

[opensearch-trigger-bot]

The backport to 2.5 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.5 2.5
# Navigate to the new working tree
cd .worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-724-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c0f7bd934b79f7c3a911229fa63e157116ec5ca9
# Push it to GitHub
git push --set-upstream origin backport/backport-724-to-2.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.5

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

[opensearch-trigger-bot]

The backport to 2.8 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.8 2.8
# Navigate to the new working tree
cd .worktrees/backport-2.8
# Create a new branch
git switch --create backport/backport-724-to-2.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c0f7bd934b79f7c3a911229fa63e157116ec5ca9
# Push it to GitHub
git push --set-upstream origin backport/backport-724-to-2.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.8

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

[opensearch-trigger-bot]

The backport to 2.6 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.6 2.6
# Navigate to the new working tree
cd .worktrees/backport-2.6
# Create a new branch
git switch --create backport/backport-724-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c0f7bd934b79f7c3a911229fa63e157116ec5ca9
# Push it to GitHub
git push --set-upstream origin backport/backport-724-to-2.6
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.6

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

[opensearch-trigger-bot]

The backport to 2.7 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.7 2.7
# Navigate to the new working tree
cd .worktrees/backport-2.7
# Create a new branch
git switch --create backport/backport-724-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c0f7bd934b79f7c3a911229fa63e157116ec5ca9
# Push it to GitHub
git push --set-upstream origin backport/backport-724-to-2.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.7

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