Sagemaker Operator Character limit fix

[dirkrkotzeml]

… SageMaker 64 character length constraint

SageMakerProcessingJobs have a hard limit of 64 characters for the ProcessingJobName.
In the SageMakerBaseOperator there is a check for uniqueness for the name.
In the case that a name is not unique it adds a timestamp to prevent a potential collision, however there is no check to prevent the updated - from exceeding 64 characters. This causes the creation of the SageMakerProcessingJob to fail.

In the SageMaker Pipelines SDK they truncate the base name before adding the timestamp, therefor we took a similar approach for consistency purposes.

Closes: #45550

[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: [email protected]
  Slack: https://s.apache.org/airflow-slack

[vincbeck]

Could you add a unit test to cover that?

[dirkrkotzeml]

Could you add a unit test to cover that?

@ferruzzi @vincbeck We have updated the prior unit tests and added two of our own, the provider tests all pass.

Just a small note the previous mock for time_ns was using an incorrect format that the time_ns() function would not return.
We updated the unit tests to use a representative integer for the tests.

In our updated function we limit the returned timestamp to 10 characters to capture only the date time up to the seconds as this is all that is needed.

[Rudolf07688]

@dirkrkotzeml @eladkal @o-nikolas
Unit tests passing after latest commit.

[Rudolf07688]

Looks exactly like how it is done on the SageMaker Pipelines SDK. Happy with it.

[ferruzzi]

Looks like you just need to run your static checks. running breeze static-checks should fix the formatting issues that the CI is crying about.

[Rudolf07688]

Looks like you just need to run your static checks. running breeze static-checks should fix the formatting issues that the CI is crying about.

Ran the checks now and pushed changes. Thanks @ferruzzi

[ferruzzi]

Congrats on your first PR

[boring-cyborg]

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