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 Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits 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.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

I think you should add/modify unit tests for the hook. Happy to Approve & Run them if you add them @piotrkmita

Hey @potiuk
thank you for your suggestion. I've updated the test_submit_timeout to have timeout=5, so status will be called at times 0, 5, 10 and check if status_check.call_count is equal 3. Also, created one more checking if default timeout is working properly if it's not set.

Does it make sense or have you meant something else?
Thanks!

I thought more about adding a test to tests/apache/druid/operators/test_druid.py not hooks/test_druid.py - to add instantiation of the operator with timout passed as parameter.

I reverted previous commit and added tests for timeout and max_ingestion_time.
Please let me know if I should improve something.
Thank you!

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

Awesome work, congrats on your first merged pull request!