Fix test assertion values to match mock data

The testToProtoWithAggregations test had incorrect expected values:
- minAgg mock returns -50.0 but assertion expected 10.0
- maxAgg mock returns 9999.0 but assertion expected 100.0

Updated assertions to match the actual mock values.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: yiyuabc

modules/transport-grpc/src/main/java/org/opensearch/transport/grpc/proto/request/common/ObjectParserProtoUtils.java

@@ -28,20 +28,7 @@ private ObjectParserProtoUtils() {
      * Declares a field, mirroring {@link org.opensearch.core.xcontent.ObjectParser#declareField(BiConsumer, org.opensearch.core.xcontent.ObjectParser.ContextParser, ParseField, org.opensearch.core.xcontent.ObjectParser.ValueType)}.
      *
      * <p>This method dispatches to the consumer when value is not null, optionally transforming
-     * the value via the parser function first. Validation happens in the consumer (setter), just like REST.
-     *
-     * <p>REST always uses a parser to extract values from the stream. In gRPC, values are already
-     * extracted from proto, so the parser is used for transformation only. For simple fields that
-     * need no transformation, use {@link Function#identity()}.
-     *
-     * <p><b>Null handling (matches REST):</b>
-     * <ul>
-     *   <li>If value is null: parser and consumer are NOT called (no-op), matching REST behavior
-     *       when a field is not present in JSON</li>
-     *   <li>If value is not null: parser transforms it, then consumer is called with the result</li>
-     *   <li>If parser returns null: consumer is STILL called - the setter is responsible for
-     *       null validation, just like REST</li>
-     * </ul>
+     * the value via the parser function first. Validation happens in the consumer, just like REST.
      *
      * @param builder The builder to set the field on
      * @param consumer The consumer to set the field value (e.g., Builder::field, Builder::missing)

modules/transport-grpc/src/main/java/org/opensearch/transport/grpc/proto/request/search/aggregation/metrics/package-info.java

@@ -5,8 +5,6 @@
 /**
  * Protocol Buffer utilities for metrics aggregation requests.
  * Contains converters from Protocol Buffer aggregation requests to OpenSearch metrics aggregation builders.
- * <p>
- * Metrics aggregations compute metrics (like min, max, avg, sum, cardinality) over a set of documents.
  *
  * @see org.opensearch.search.aggregations.metrics
  */

modules/transport-grpc/src/test/java/org/opensearch/transport/grpc/proto/response/search/SearchResponseSectionsProtoUtilsTests.java

@@ -365,13 +365,13 @@ public void testToProtoWithAggregations() throws IOException {
         org.opensearch.protobufs.Aggregate minAggregate = protoResponse.getAggregationsOrThrow("min_price");
         assertTrue("Min should have value", minAggregate.hasValue());
         assertTrue("Min value should be double", minAggregate.getValue().hasDouble());
-        assertEquals("Min value should be 10.0", 10.0, minAggregate.getValue().getDouble(), 0.001);
+        assertEquals("Min value should be -50.0", -50.0, minAggregate.getValue().getDouble(), 0.001);
 
         // Verify Max aggregation
         org.opensearch.protobufs.Aggregate maxAggregate = protoResponse.getAggregationsOrThrow("max_price");
         assertTrue("Max should have value", maxAggregate.hasValue());
         assertTrue("Max value should be double", maxAggregate.getValue().hasDouble());
-        assertEquals("Max value should be 100.0", 100.0, maxAggregate.getValue().getDouble(), 0.001);
+        assertEquals("Max value should be 9999.0", 9999.0, maxAggregate.getValue().getDouble(), 0.001);
     }
 
     public void testToProtoWithNullAggregations() throws IOException {