Bug: BigQuery connection UI defaults 'Use Legacy SQL' to true on edit

[kandharvishnu]

Apache Airflow version

2.10.5

If "Other Airflow 2 version" selected, which one?

No response

What happened?

The "Use Legacy SQL" checkbox is selected Automatically as the default value

connection_form_widgets["use_legacy_sql"] = BooleanField(lazy_gettext("Use Legacy SQL"), default=True)

What you think should happen instead?

The default value should be removed.

How to reproduce

1. While creating a new BigQuery connection, uncheck the "Use Legacy SQL" option.

2. Save the connection — the value is correctly stored as 'use_legacy_sql': False in the extra_dejson field.

   

3. Reopen the saved connection (without changing anything), and observe that "Use Legacy SQL" is selected again.

   

4. If you click Save at this point, the value is incorrectly persisted as 'use_legacy_sql': True.

   

Operating System

"Debian GNU/Linux 12 (bookworm)"

Versions of Apache Airflow Providers

apache-airflow-providers-google==14.1.0

Deployment

Astronomer

Deployment details

Local deployment

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[kandharvishnu]

#49038

[Mayuresh16]

@potiuk @rawwar @kandharvishnu
I think we should close this issue, as the fix is already merged.
Linked PR: #49038