[JavaClient][OAP] Improve Index Performance By Setting "no_sort"

[hanahmily]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

BanyanDB IndexRule supports the option to set no_sort to exclude sorted tables from the underlying index files. This field should be set to 'true' if the data does not need to be sorted based on a specific index.

For the Java client, sync the proto file to include support for this field.
For OAP, set this field to true for indexes that do not require sorting support.

Use case

No response

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

I am not sure how to use this in OAP.
AFAIK, there isn't proper setting in OAP model to describe this.

[wu-sheng]

@BanyanDB.NoSort could be considered.

Possible use cases should be similar with @ElasticSearch.DisableDocValues annotation, introduced in #12741

1. Value column of metrics. This is not necessary in BanyanDB, as value column is different.
2. Conditions of logs and traces(skywalking and zipkin) exclude latency and timestamp, which are used in sorting.
3. All searchable field in metadata(*_traffic)

@hanahmily Please check both sides. I think separating two storage with making this concept more clear.

[wu-sheng]

@mrproliu As you have more time, please take a look at this after #12685
We should consider @BanyanDB.Sortable annotation because it seems all tag fields of BanyanDB. Only the tag is being used for query(e.g. latency in segment), we should add this annotation to activate it.