Module matched 

The DataFusion and sqlparser messages the engine and the CLI recognize by their text, because no typed error says the same (#265).

Each is matched as a substring or a prefix, as its doc says. The tests below trigger each message in DataFusion or sqlparser directly, not through Ursa’s wrappers, and check the text is still there: when an upgrade changes the wording, they fail and name the string to update.

Constants

NO_FILES_FOR_TABLE

In the error ListingTableConfig::infer_options returns when a location lists no file (an internal error). Ursa says “no file found at ‘…’” instead (file_table.rs).

NO_FILE_FORMAT_FOR_EXTENSION

In the error ListingTableConfig::infer_options returns for a file whose extension names no format it knows. Ursa lists the formats it reads instead (file_table.rs).

OPTIMIZER_RULE_FAILED

The start of the context DataFusion’s optimizer puts on a rule’s error (Optimizer rule '…' failed). Which rule failed is DataFusion’s business: super::user_message drops it and keeps the cause.

TOKENIZER_EOF

In sqlparser’s tokenizer error for a quoted identifier or a block comment still open at the end of the input (… before EOF., Unexpected EOF while in a multi-line comment). The shell reads the next line instead (ursa-cli’s input.rs).

TOKENIZER_UNTERMINATED

The start of sqlparser’s tokenizer error for a string literal (or a dollar-quoted or encoded one) still open at the end of the input. The shell reads the next line instead of reporting it (ursa-cli’s input.rs).