[PROPOSAL] Renaming the "similarity" option in the Top N queries grouping configuration dropdown

[KishoreKicha14]

What/Why

What are you proposing?

We propose renaming the "similarity" option in the Top N queries grouping configuration dropdown to "Query Size" to more accurately reflect its functionality.

What users have asked for this feature?

While specific user requests are not mentioned, this change addresses potential confusion in the current user interface. It aligns with best practices for clear and intuitive UI labeling.

What problems are you trying to solve?

When configuring query grouping, users want to understand clearly what each option does, so they can make appropriate choices for their analysis needs. The current "similarity" label is ambiguous and may not accurately convey that it groups queries based on their size.

What is the developer experience going to be?

This change primarily affects the UI labeling. Developers will need to update the dropdown option text from "similarity" to "Query Size" in the relevant UI components.

Are there any security considerations?

There are no security implications for this labeling change.

Are there any breaking changes to the API

no

What is the user experience going to be?

Users will see "Query Size" instead of "similarity" in the grouping configuration dropdown, providing a clearer understanding of the grouping mechanism.

Are there breaking changes to the User Experience?

This is a minor change that improves clarity without significantly altering the user flow or experience.

Why should it be built? Any reason not to?

Describe the value that this feature will bring to the OpenSearch community, as well as what impact it has if it isn't built, or new risks if it is. Highlight opportunities for additional research.

What will it take to execute?

Describe what it will take to build this feature. Are there any assumptions you may be making that could limit scope or add limitations? Are there performance, cost, or technical constraints that may impact the user experience? Does this feature depend on other feature work? What additional risks are there?

Any remaining open questions?

What are known enhancements to this feature? Any enhancements that may be out of scope but that we will want to track long term? List any other open questions that may need to be answered before proceeding with an implementation.