fix

Signed-off-by: Yuri Shkuro <[email protected]>

proto/api_v2/query.proto

@@ -50,7 +50,7 @@ message GetTraceRequest {
     (gogoproto.stdtime) = true,
     (gogoproto.nullable) = false
   ];
-  // Optional. If set to true, the response will not perform any 
+  // Optional. If set to true, the response will not include any
   // enrichments to the trace, such as clock skew adjustment.
   // Instead, the trace will be returned exactly as stored.
   bool raw_traces = 4;
@@ -116,7 +116,7 @@ message TraceQueryParameters {
     (gogoproto.nullable) = false
   ];
   int32 search_depth = 8;
-  // Optional. If set to true, the response will not perform any 
+  // Optional. If set to true, the response will not include any
   // enrichments to the trace, such as clock skew adjustment.
   // Instead, the trace will be returned exactly as stored.
   bool raw_traces = 9;

proto/api_v3/query_service.proto

@@ -34,7 +34,7 @@ message GetTraceRequest {
   // Optional. The end time to search trace ID.
   google.protobuf.Timestamp end_time = 3;
 
-  // Optional. If set to true, the response will not perform any 
+  // Optional. If set to true, the response will not include any
   // enrichments to the trace, such as clock skew adjustment.
   // Instead, the trace will be returned exactly as stored.
   bool raw_traces = 4;
@@ -78,7 +78,7 @@ message TraceQueryParameters {
   // the larger depth value simply means more traces returned.
   int32 search_depth = 8;
 
-  // If set to true, the response will not perform any 
+  // Optional. If set to true, the response will not include any
   // enrichments to the trace, such as clock skew adjustment.
   // Instead, the trace will be returned exactly as stored.
   bool raw_traces = 9;

swagger/api_v3/query_service.swagger.json

@@ -132,6 +132,13 @@
             "required": false,
             "type": "integer",
             "format": "int32"
+          },
+          {
+            "name": "query.raw_traces",
+            "description": "Optional. If set to true, the response will not include any \nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored.",
+            "in": "query",
+            "required": false,
+            "type": "boolean"
           }
         ],
         "tags": [
@@ -186,7 +193,7 @@
           },
           {
             "name": "raw_traces",
-            "description": "Optional. If set to true, the response will not perform any \nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored.",
+            "description": "Optional. If set to true, the response will not include any \nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored.",
             "in": "query",
             "required": false,
             "type": "boolean"
@@ -364,7 +371,7 @@
         },
         "raw_traces": {
           "type": "boolean",
-          "description": "If set to true, the response will not perform any \nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored."
+          "description": "Optional. If set to true, the response will not include any \nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored."
         }
       },
       "description": "Query parameters to find traces. Except for num_traces, all fields should be treated\nas forming a conjunction, e.g., \"service_name='X' AND operation_name='Y' AND ...\".\nAll fields are matched against individual spans, not at the trace level.\nThe returned results contain traces where at least one span matches the conditions.\nWhen num_traces results in fewer traces returned, there is no required ordering.\n\nNote: num_traces should restrict the number of traces returned, but not all backends\ninterpret it this way. For instance, in Cassandra this limits the number of _spans_\nthat match the conditions, and the resulting number of traces can be less.\n\nNote: some storage implementations do not guarantee the correct implementation of all parameters."