Feature/QueryGroup Add CRUD APIs in plugin

[ruai0511]

Description

As part of limiting the resource usage to the group of queries(QueryGroup). The feature is broken down into 3 independent parts.

• CRUD APIs (Will go into the Plugin)
• Request Tagging/Classification (Will go into the Plugin)
• Tracking and Monitoring

This change consists of the CRUD APIs and the UTs

The Create QueryGroup API schema is:

curl -XPUT "localhost:9200/_query_group/" -H 'Content-Type: application/json' -d ' 
{
     "name": "analytics",
     "jvm":0.4,
     "mode": "monitor"
}'

The Update QueryGroup API schema is:

curl -XPUT "localhost:9200/_query_group/analytics" -H 'Content-Type: application/json' -d ' 
{
     "jvm":0.4, (optional)
     "mode": "monitor" (optional)
}'

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]

❌ Gradle check result for ea727b9: 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 4182e07: 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 6cc94e2: 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 43dec36: 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 fd9ecee: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[jainankitk]

@ruai0511 - Thank you for creating this PR. Can you update the title/description with recent name (query group) and schema.

[jainankitk]

@ruai0511 - This single PR has too many changes. May I suggest breaking this down into multiple PRs as below:

• QueryGroup infra changes like PersistenceService, Pruner and other files
• Create/Delete APIs for QueryGroup
• Get/Update API changes for QueryGroup

In addition to making the code review much easier, keeping the PR short also makes it easy to root cause regressions (if any) discovered from the nightly benchmarks or any other mechanisms

[jainankitk]

Need to update the schema to most recent one

[ruai0511]

This schema is the most recent one. The schema in QueryGroup (pasted below) is how we want to store the querygroup internally, it has id on the outside so users shouldn't use that schema when creating a querygroup.

/**
 * Class to define the QueryGroup schema
 * {
 *     "fafjafjkaf9ag8a9ga9g7ag0aagaga" : {
 *              "jvm": 0.4,
 *              "mode": "enforced",
 *              "name": "analytics",
 *              "updatedAt": 4513232415
 *      }
 * }
 */

[github-actions]

❌ Gradle check result for fd9ecee: 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?

[ruai0511]

@ruai0511 - This single PR has too many changes. May I suggest breaking this down into multiple PRs as below:

• QueryGroup infra changes like PersistenceService, Pruner and other files
• Create/Delete APIs for QueryGroup
• Get/Update API changes for QueryGroup

In addition to making the code review much easier, keeping the PR short also makes it easy to root cause regressions (if any) discovered from the nightly benchmarks or any other mechanisms

I considered separating the

@ruai0511 - This single PR has too many changes. May I suggest breaking this down into multiple PRs as below:

• QueryGroup infra changes like PersistenceService, Pruner and other files
• Create/Delete APIs for QueryGroup
• Get/Update API changes for QueryGroup

In addition to making the code review much easier, keeping the PR short also makes it easy to root cause regressions (if any) discovered from the nightly benchmarks or any other mechanisms

Turned out that I couldn't do a infra PR, because the persistence service depends on the API classes. I'm able to seperate this PR into four smaller PR though - each with one API.