1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
//! Low-cardinality error taxonomy for observability (issue #1038).
//!
//! This taxonomy is intentionally distinct from [`crate::error::ErrorCategory`]:
//! that one is a 14-variant developer-facing grouping consumed by the CLI and
//! existing tests, and changing it would break public API. The taxonomy here is
//! the *telemetry* taxonomy — a small, stable, bounded set of `&'static str`
//! labels safe to use as a metric/span attribute value (see
//! [`crate::observability::catalog::attr::ERROR_CATEGORY`]).
//!
//! # Taxonomy
//!
//! | Variant | `as_str()` | Maps from `cqlite_core::Error` … |
//! |----------------|------------------|-------------------------------------------------------------------|
//! | `Io` | `io` | `Io`, `InvalidPath`, `Timeout` |
//! | `Serialization`| `serialization` | `Serialization`, `TypeConversion` |
//! | `Corruption` | `corruption` | `Corruption`, `CorruptCommitLogFrame`, `ColumnDecode` |
//! | `Schema` | `schema` | `Schema`, `Table` |
//! | `Parsing` | `parsing` | `Parse`, `CqlParse`, `InvalidFormat`, `UnsupportedFormat`, |
//! | | | `UnsupportedVersion`, `UnsupportedCommitLogVersion` |
//! | `Storage` | `storage` | `Storage`, `Memory`, `Index`, `Compaction`, `WriteDirLocked` |
//! | `Concurrency` | `concurrency` | `Concurrency`, `Transaction` |
//! | `Constraints` | `constraints` | `ConstraintViolation`, `AlreadyExists` |
//! | `Query` | `query` | `QueryExecution`, `UnsupportedQuery`, `InvalidInput`, |
//! | | | `ResultTooLarge`, `ForcedReadPathUnavailable`, `InvalidReadPath` |
//! | `Cancelled` | `cancelled` | `Cancelled` (issue #2264 — a cooperative abort, never `Io`) |
//! | `Timeout` | `timeout` | `QueryTimeout` (issue #1695 — an operator budget, never data) |
//! | `Other` | `other` | `Configuration`, `InvalidState`, `InvalidOperation`, `NotFound`, |
//! | | | `Internal`, `Wasm` (`wasm32` builds only) |
//!
//! The table is EXACT, not illustrative: every row's `Maps from` column lists the
//! COMPLETE set of `Error` variants [`classify`] routes to that category, `Other`
//! included. There is **no catch-all**. [`classify`] matches on `&Error` with every
//! arm an explicit `Error::<Variant>` pattern (pinned by
//! `error_schema_tests::classify_has_no_catch_all_arm`), so a newly-added `Error`
//! variant is a COMPILE ERROR until it is categorised by hand — it is never
//! silently absorbed into `Other`. `Wasm` is `#[cfg(target_arch = "wasm32")]`-gated
//! and therefore exists only in `wasm32` builds; it is listed because the table
//! describes the enum, not one target.
//!
//! `error_schema_tests::every_error_variant_classify_routes_is_documented_in_the_taxonomy_table`
//! enforces variant→category set equality against [`classify`]'s match arms in
//! both directions (issue #1705, AI5 of epic #1686): a variant routed but
//! undocumented, a documented variant that is never routed, and a variant listed
//! under the wrong category all fail. The `Maps from` column is parsed
//! fail-closed — a non-parenthetical item that is not a backticked variant name,
//! or a parenthetical that claims catch-all behaviour, reds the guard rather than
//! being silently dropped as prose (which is how the stale "any future variant
//! (catch-all)" claim survived here).
//!
//! **Scope: telemetry only.** The language bindings do NOT derive from
//! [`classify`]: `cqlite_ffi_common::error_contract` (issue #1451) mirrors the distinct
//! [`Error::category`](crate::error::Error::category) enum, and nothing pins the
//! two together — `QueryTimeout` is `Timeout` here and `Query` there.
//!
//! # Relation to spans and CLI exit codes
//!
//! - **Spans**: [`crate::observability::record_error`] attaches the
//! `as_str()` value as the `cqlite.error.category` attribute on the
//! `cqlite.errors.total` counter and as a span event field, and marks the
//! current span `otel.status_code = ERROR`.
//! - **CLI exit codes** (`cqlite-cli/src/error.rs`): the CLI maps the *raw*
//! `Error` variants to numeric exit codes (2/3/4/5/6). This taxonomy is a
//! coarser, monitoring-oriented view; the rough correspondence is:
//! `Schema → exit 3`, `Io`/`Storage` → exit 4, `Query`/`Parsing` → exit 5.
//! The two are deliberately decoupled: exit codes are an operator contract,
//! the telemetry taxonomy is tuned for dashboards/alerts.
use crateError;
/// Bounded, telemetry-safe error categories. The total count is small and
/// fixed, making `as_str()` values safe as metric/span attribute values.
/// Map a [`cqlite_core::Error`](crate::error::Error) to its telemetry
/// [`ObsErrorCategory`]. This is the single classification point; both
/// `Error::obs_category` and `record_error` route through it.
pub
/// Invariant + code↔doc completeness tests live in a sibling file so this file
/// stays pure source inside the campsite-rule target (#1116); they are logically
/// the `tests` submodule of this module.