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

Thanks @Aditi102005 !!

The import statement airflow.configuration present in jdbc here and here

If possible we can update these statements

Static checks are failing !! Could you please fix them ?

You have issues to fix - > both MyPy and regular static checks (which can be fixed with prek)

I’m working on Windows where some prek hooks (including mypy-providers and UI-related hooks) fail locally due to path/node limitations.
I’ve pushed a commit to trigger CI, which runs all MyPy and static checks on Linux.

Need to fix static checks. (You can also check locally with prek run -a ruff-format, this one should work on Windows.)

@Aditi102005, this PR needs a fix for static checks.

Hello @Aditi102005 -

The same static errors persist, unfortunately. It will be great to follow steps as per the documentation link mentioned below, to use WSL/Linux on your Windows machine, so no one has to suggest changes to you.
"prek" will fix the static errors for you by default, hence the time taken to merge your PR will be drastically reduced.

I was in same boat as you and after implementing as per steps in below link, have set up to be able run static checks from my end, before any PR commits. Please feel free to post any blockers in Slack channel #new-contributors, so the community can help out.

https://github.com/apache/airflow/blob/main/contributing-docs/03_contributors_quick_start.rst

For the static error, if you observe closely, there is a line between the lines "requires-python = ">=3.10"" and "# The dependencies should be modified in place in the generated file." that got introduced as a typo when you were making changes, causing the static checks to fail. As mentioned above by everyone, using "prek" fixes any static checks automatically.

Good luck!

@Aditi102005 PR should not change any files in airlfow-core nor task-sdk paths. Seems like a bad rebase?

Thanks for the clarification.
The previous branch was not based on a clean upstream/main.
I’ve opened a new PR with only the JDBC provider changes on top of the latest upstream/main.