Skip to content

fix(go/adbc/pkg): treat the "warn" log level as warning - #4881

Merged
lidavidm merged 1 commit into
apache:mainfrom
HyukjinKwon:fix-warn-log-level
Oct 12, 2026
Merged

lidavidm merged 1 commit into
apache:mainfrom
HyukjinKwon:fix-warn-log-level

Conversation

@HyukjinKwon

@HyukjinKwon HyukjinKwon commented Oct 12, 2026 •

Copy link
Copy Markdown
Member

case "warn": had no body, so warn kept the error level. Fold it into the warning case in the template, and apply the same change to the generated Flight SQL and panicdummy drivers.

Closes #4880

Generated-by: Isaac

"warn", the value the logging help text suggests, fell into an empty case,
so ADBC_DRIVER_<PREFIX>_LOG_LEVEL=warn kept the error level.

Co-authored-by: Isaac <no-reply@databricks.com>
lidavidm pushed a commit to adbc-drivers/driverbase-go that referenced this pull request Oct 12, 2026
`case "warn":` had no body, so `ADBC_DRIVER_<PREFIX>_LOG_LEVEL=warn`,
one of the values the logging help text suggests, kept the error level.
Fold it into the `warning` case.

Reported in adbc-drivers/spark#96. The template came from
apache/arrow-adbc, which has the same bug (apache/arrow-adbc#4881).

Generated-by: Isaac <no-reply@databricks.com>
@lidavidm
lidavidm merged commit d98fc62 into apache:main Oct 12, 2026
55 checks passed
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.

go/adbc/pkg: the "warn" log level keeps the error level

2 participants