You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cli.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,6 +133,8 @@ The output from `EXPLAIN ANALYZE` provides a wealth of information on a queries
133
133
134
134
To help with this the `--analyze` flag can used to generate a summary of the underlying `ExecutionPlan``MetricSet`s. The summary presents the information in a way that is hopefully easier to understand and easier to draw conclusions on a query's performance.
135
135
136
+
**Important**: The analyze feature only supports a single SQL statement. If you provide multiple statements (e.g., separated by semicolons) or multiple files/commands, an error will be returned.
137
+
136
138
This feature is still in it's early stages and is expected to evolve. Once it has gone through enough real world testing and it has been confirmed the metrics make sense documentation will be added on the exact calculations - until then the source will need to be inspected to see the calculations.
Copy file name to clipboardExpand all lines: docs/flightsql_analyze_protocol.md
+41-37Lines changed: 41 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,8 @@ The FlightSQL Analyze Protocol enables clients to retrieve detailed execution me
27
27
28
28
**Request Body**: UTF-8 encoded SQL query string
29
29
30
+
**Important**: The SQL query must contain exactly one SQL statement. Multiple statements (e.g., separated by semicolons) are not supported and will result in an error.
31
+
30
32
**Example**:
31
33
```rust
32
34
Action {
@@ -39,29 +41,20 @@ Action {
39
41
40
42
### Response Format
41
43
42
-
The response is a stream of `arrow_flight::Result` messages. Each `Result.body` contains serialized `FlightData` messages. The stream provides two Arrow RecordBatches:
43
-
44
-
#### Batch 1: Queries Batch
44
+
The response is a stream of `arrow_flight::Result` messages. Each `Result.body` contains serialized `FlightData` messages.
45
45
46
-
**Purpose**: Contains the analyzed query text
46
+
#### Response Metadata
47
47
48
-
**Schema**:
49
-
| Column | Type | Nullable | Description |
50
-
|--------|------|----------|-------------|
51
-
| query | Utf8 | false | The SQL query that was analyzed |
48
+
The first `FlightData` message (schema message) contains the query text in its metadata:
0 commit comments