[Feature Request] Supports RangeQueryBuilder lte, gte method provide "lte", "gte" operator, not "from", "to"

[roharon]

Is your feature request related to a problem? Please describe

In OpenSearch 2.14.0.

When I define query with RangeQueryBuilder, gte and gt method defined query tofrom, and lteand lt method defined query to to.

I think defined query to gte, gt or lte, lt is more properly.

Describe the solution you'd like

When I write code as

RangeQueryBuilder("name").gte(LocalDate.of(2024, 6, 10)).lte(LocalDate.of(2024, 6, 13))

actual result is

{
  "range": {
    "name": {
      "from": "2024-06-10",
      "to": "2024-06-13",
      "include_lower": true,
      "include_upper": true,
    }
  }
}  

But I think this result should be like below.

{
  "range": {
    "name": {
      "gte": "2024-06-10",
      "lte": "2024-06-13"
    }
  }
}  

Related component

Libraries

Describe alternatives you've considered

No response

Additional context

No response

[dblock]

[Catch All Triage - Attendees 1, 2, 3, 4, 5]

[msfroh]

These are equal objects. Why does it matter what the JSON representation of a RangeQueryBuilder is?

The gt, lt, gte, and lte parameters are intended as a convenient short-hand for the more verbose from, to, include_lower, include_upper representations.

[roharon]

These are equal objects. Why does it matter what the JSON representation of a RangeQueryBuilder is?

The gt, lt, gte, and lte parameters are intended as a convenient short-hand for the more verbose from, to, include_lower, include_upper representations.

gt is same as setting from and include_lower to false. and also gte is same as setting from and include_lower to true. the same goes for lt,lte.

Even though, when defined query with gte, it would be expected, and more natural as gte not from and include_lower: true