dannycjones commented on code in PR #5110:
URL: https://github.com/apache/hadoop/pull/5110#discussion_r1021284548


##########
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/audit/impl/LoggingAuditor.java:
##########
@@ -230,6 +240,26 @@ private class LoggingAuditSpan extends 
AbstractAuditSpanImpl {
 
     private final HttpReferrerAuditHeader referrer;
 
+    /**
+     * Attach Range of data for GetObject Request.
+     * @param request given get object request
+     */
+    private void attachRangeFromRequest(AmazonWebServiceRequest request) {
+      if (request instanceof GetObjectRequest) {
+        long[] rangeValue = ((GetObjectRequest) request).getRange();
+        if (rangeValue == null || rangeValue.length == 0) {
+          return;
+        }
+        if (rangeValue.length != 2) {
+          WARN_INCORRECT_RANGE.warn("Expected range to contain 0 or 2 
elements. Got "
+              + rangeValue.length + " elements. Ignoring");
+          return;
+        }
+        String combinedRangeValue = String.format("bytes=%d-%d", 
rangeValue[0], rangeValue[1]);

Review Comment:
   @steveloughran, can you elaborate on the `rg` prefix? Is it for the query 
parameter? If so, we already have that as `r` (`PARAM_RANGE`).
   
   `bytes=` is part of the range header value which - following the SDK upgrade 
- can just be dumped in place, without needing reconstruction like this.
   
   That being said, it does seem a bit of a waste. Maybe we drop it entirely 
here (and for all connectors) and just include whatever the value of the range 
header was minus `bytes=` prefix.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to