Skip to content

fix(query): stop logging a missing column at ERROR - #129

Open
kdembler wants to merge 1 commit into
masterfrom
fix/query-missing-column-log
Open

kdembler wants to merge 1 commit into
masterfrom
fix/query-missing-column-log

Conversation

@kdembler

Copy link
Copy Markdown

Problem

When a query selects a column the parquet file lacks, the scan logs column 'x' is not found in <table> at ERROR and then returns ColumnDoesNotExist with the same table and column.

For a worker this is a client mistake: the query asks for a field the chunk predates, and the worker answers bad_request. The ERROR line still lands in the operator's log and in Sentry, where it reads as a worker fault.

Change

The scan no longer logs the miss. It returns ColumnDoesNotExist as before, so the caller decides whether and at what level to log it.

🤖 Generated with Claude Code

The scan returns ColumnDoesNotExist, which carries the same table and column,
so the caller decides whether the miss is worth a log line. A worker serving a
query for a field its chunk predates answers bad_request, and the ERROR line
made that client mistake read as a worker fault in the operator's log and in
Sentry.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant