Added size attribute to MultiTermsAggregation

[fabiankopatschek]

Description

Added size attribute to MultiTermsAggregation to retreive other hit sizes than the default value of the attribute.
Code for the added attribute was taken from TermsAggregation class.
This pull request replaces #614, as dblock suggested that the changes should go to the main branch.
Please backfort this code to 2.x.

Issues Resolved

• [FEATURE] Support bucket size for MultiTermAggregation #534

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[VachaShah]

@fabiankopatschek Thank you for adding this! Some integ tests related to aggregations are failing. Can you take a look?

[fabiankopatschek]

@fabiankopatschek Thank you for adding this! Some integ tests related to aggregations are failing. Can you take a look?

@VachaShah I did some manual testing and some research. The multi_terms feature was implemented with version 2.1.0 of opensearch.
Is there a mechanism to run specific integration tests only against a specified minimum version of opensearch?

[VachaShah]

@fabiankopatschek Thank you for adding this! Some integ tests related to aggregations are failing. Can you take a look?

@VachaShah I did some manual testing and some research. The multi_terms feature was implemented with version 2.1.0 of opensearch. Is there a mechanism to run specific integration tests only against a specified minimum version of opensearch?

Yes, you can do something similar to https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/test/java/org/opensearch/client/opensearch/integTest/AbstractRequestIT.java#L633.

[fabiankopatschek]

@fabiankopatschek Thank you for adding this! Some integ tests related to aggregations are failing. Can you take a look?

@VachaShah I did some manual testing and some research. The multi_terms feature was implemented with version 2.1.0 of opensearch. Is there a mechanism to run specific integration tests only against a specified minimum version of opensearch?

Yes, you can do something similar to https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/test/java/org/opensearch/client/opensearch/integTest/AbstractRequestIT.java#L633.

@VachaShah Thank you for the link.
I added this part to the failing integrationTests and did some local testing with 1.3.12 and 2.5.0.

[VachaShah]

@fabiankopatschek Thank you for adding this! Some integ tests related to aggregations are failing. Can you take a look?

@VachaShah I did some manual testing and some research. The multi_terms feature was implemented with version 2.1.0 of opensearch. Is there a mechanism to run specific integration tests only against a specified minimum version of opensearch?

Yes, you can do something similar to https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/test/java/org/opensearch/client/opensearch/integTest/AbstractRequestIT.java#L633.

@VachaShah Thank you for the link. I added this part to the failing integrationTests and did some local testing with 1.3.12 and 2.5.0.

Looks great! Can you rebase and fix the merge conflicts in Changelog and we are good to go.

[fabiankopatschek]

@fabiankopatschek Thank you for adding this! Some integ tests related to aggregations are failing. Can you take a look?

@VachaShah I did some manual testing and some research. The multi_terms feature was implemented with version 2.1.0 of opensearch. Is there a mechanism to run specific integration tests only against a specified minimum version of opensearch?

Yes, you can do something similar to https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/test/java/org/opensearch/client/opensearch/integTest/AbstractRequestIT.java#L633.

@VachaShah Thank you for the link. I added this part to the failing integrationTests and did some local testing with 1.3.12 and 2.5.0.

Looks great! Can you rebase and fix the merge conflicts in Changelog and we are good to go.

Done :)