Make sqlalchemy an optional dependency for Impala provider

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hohshho]

Closes: #59898
Related: #59895

What does this PR do?

This PR makes sqlalchemy an optional dependency for the Impala provider.
The import in ImpalaHook is now wrapped in a try/except block, and it raises an AirflowOptionalProviderFeatureException if sqlalchemy is not installed when accessed.

Why is this needed?

This aligns the Impala provider with Airflow's standard for task isolation and core dependency removal. By making sqlalchemy optional, we ensure that the provider can run in lightweight environments where sqlalchemy is not strictly required, unless the user explicitly needs features that depend on it (e.g., get_uri or specific SQL connection helpers).

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Srabasti]

Line 73 should be referencing "sqlalchemy>=1.4.49" instead of "sqlalchemy>=1.4.0".
Happy New Year!

[hohshho]

Updated the minimum SQLAlchemy version to 1.4.49 as suggested. Thanks!

[Srabasti]

LGTM - Thanks for incorporating the changes @hohshho!

[potiuk]

Approve but there is one NIT to take a look.

[potiuk]

One more small nit - after @Prab-27 comment I realized that kerberos one could be fixed as well :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.