regenerate

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

swagger/api_v3/query_service.swagger.json

@@ -135,7 +135,7 @@
           },
           {
             "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.",
+            "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"
@@ -193,7 +193,7 @@
           },
           {
             "name": "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.",
+            "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"
@@ -371,7 +371,7 @@
         },
         "raw_traces": {
           "type": "boolean",
-          "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": "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."