Checking modification timestamps only when newer_than is present

[kkulczak]

…esent

Checking modification timestamps has sagnificant impact on performance of sensors in ase of large amount of files.
This whole block of code do not need to be executed, when newer_than=None

---

^ 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 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 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.
• 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

[kkulczak]

Done. Please consider merging.
If merged when can I expect the release with this change? I need to inform my customer

[potiuk]

NIT: Is it also possible to have a test that shows that it IS called when newer_than is set?

Done. Please consider merging. If merged when can I expect the release with this change? I need to inform my customer

With the next provider's release. We usually release every 2 weeks or so (see the docs about providers) but this is on a best-effort base and we are about to release Airlfow 3 so that might be skewed. This is open-source, no promises can be made with those as most people work here as volunteers.

[potiuk]

And you are not blocked. You are absolutely free to build your own provider version. Providers are absolutely standard packages now - with their own pyproject.toml files and you can easily build your own distribution packages.

Also breeze release-management prepare-providers-distributions allows you to build providers locally easily - and you can have your customer to install such providers prepared by you without waiting for release if you do not want to wait.

[kkulczak]

@potiuk

NIT: Is it also possible to have a test that shows that it IS called when newer_than is set?

Done

Regarding release, thanks for letting me know :)

[kkulczak]

Cheked tests passing on github codespace.
Cannot

[kkulczak]

Could you re-run pipeline please?

[kkulczak]

Are there any actions needed from my side?

[boring-cyborg]

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

[potiuk]

Just delays due to Airflow 3 :)