OTel Metric fixes (#1271)

* Fixed the main Data Prepper build by fixing Javadoc errors in OTelMetricsProtoHelper. Signed-off-by: David Venable <[email protected]> * Fix the Data Prepper end-to-end tests by using Armeria 1.9.2 in OTel Metrics Raw Processor. Signed-off-by: David Venable <[email protected]>
opensearch-project · Apr 6, 2022 · 5d3ff6d · 5d3ff6d
1 parent 0eaae6b
commit 5d3ff6d
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 4 deletions.
diff --git a/data-prepper-plugins/otel-metrics-raw-processor/build.gradle b/data-prepper-plugins/otel-metrics-raw-processor/build.gradle
@@ -15,8 +15,8 @@ dependencies {
     testImplementation project(':data-prepper-api').sourceSets.test.output
     implementation "io.opentelemetry:opentelemetry-proto:${versionMap.opentelemetryProto}"
     implementation 'com.google.protobuf:protobuf-java-util:3.19.4'
-    implementation "com.linecorp.armeria:armeria:1.14.1"
-    implementation "com.linecorp.armeria:armeria-grpc:1.14.1"
+    implementation "com.linecorp.armeria:armeria:1.9.2"
+    implementation "com.linecorp.armeria:armeria-grpc:1.9.2"
     implementation 'com.fasterxml.jackson.core:jackson-databind'
     implementation 'com.fasterxml.jackson.dataformat:jackson-dataformat-yaml'
     implementation group: 'com.google.guava', name: 'guava', version: '31.0.1-jre'

diff --git a/...ain/java/com/amazon/dataprepper/plugins/processor/otelmetrics/OTelMetricsProtoHelper.java b/...ain/java/com/amazon/dataprepper/plugins/processor/otelmetrics/OTelMetricsProtoHelper.java
@@ -204,12 +204,14 @@ public static List<Quantile> getQuantileValues(List<SummaryDataPoint.ValueAtQuan
      * <p>
      * The boundaries for bucket at index i are:
      * <p>
+     * <pre>{@code
      * (-infinity, explicit_bounds[i]) for i == 0
      * (explicit_bounds[i-1], +infinity) for i == size(explicit_bounds)
      * (explicit_bounds[i-1], explicit_bounds[i]) for 0 < i < size(explicit_bounds)
+     * }</pre>
      *
-     * <br/>
-     * <br/>
+     * <br>
+     * <br>
      * <b>NOTE:</b> here we map infinity as +/- FLOAT.MAX_VALUE since JSON rfc4627 only supports finite numbers and
      * OpenSearch maps double values to floats as per default.
      *