[Feature] Add the ability to configure record limit/count from the UI

[szkly]

Description

Enable users to configure record limit/count for their report definitions (based on saved searches) from the UI. The default limit (10000) can be overriden for both new and already existing reports.

Snapshots have also been updated to comply with the layout changes.

Issues Resolved

fix #328

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc 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.

[joshuali925]

thanks

[Swiddis]

Thanks for the contribution! Sorry we didn't get back sooner, got lost in the backlog. We went ahead and fast-tracked this to get merged into 2.17, which is releasing in a few days so there wasn't really enough time left to do proper review-revision cycles. I fixed merge conflicts and added some warning text for large limits based on reviewing with the team and some local testing.

Thanks again!

[opensearch-trigger-bot]

The backport to 2.x failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/dashboards-reporting/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/dashboards-reporting/backport-2.x
# Create a new branch
git switch --create backport/backport-395-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d4f95c906974b6e65fb2298f912b4327604102c3
# Push it to GitHub
git push --set-upstream origin backport/backport-395-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-reporting/backport-2.x

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

[opensearch-trigger-bot]

The backport to 2.17 failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/dashboards-reporting/backport-2.17 2.17
# Navigate to the new working tree
pushd ../.worktrees/dashboards-reporting/backport-2.17
# Create a new branch
git switch --create backport/backport-395-to-2.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d4f95c906974b6e65fb2298f912b4327604102c3
# Push it to GitHub
git push --set-upstream origin backport/backport-395-to-2.17
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-reporting/backport-2.17

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

[Swiddis]

Backports: #427 #428