potiuk opened a new issue #19414:
URL: https://github.com/apache/airflow/issues/19414


   ### Body
   
   I have a kind request for all the contributors to the latest provider 
packages release.
   Could you help us to test the RC versions of the providers and let us know 
in the comment,
   if the issue is addressed there.
   
   ## Provider [amazon: 
2.4.0rc1](https://pypi.org/project/apache-airflow-providers-amazon/2.4.0rc1)
      - [ ] [MySQLToS3Operator add support for parquet format 
(#18755)](https://github.com/apache/airflow/pull/18755): @guotongfei
      - [ ] [Add RedshiftSQLHook, RedshiftSQLOperator 
(#18447)](https://github.com/apache/airflow/pull/18447): @Brooke-white
      - [ ] [Remove extra postgres dependency from AWS Provider 
(#18844)](https://github.com/apache/airflow/pull/18844): @mariotaddeucci
      - [ ] [Remove duplicated code on S3ToRedshiftOperator 
(#18671)](https://github.com/apache/airflow/pull/18671): @mariotaddeucci
      - [ ] [Fixing ses email backend 
(#18042)](https://github.com/apache/airflow/pull/18042): @ignaski
      - [ ] [Fixup string concatenations 
(#19099)](https://github.com/apache/airflow/pull/19099): @blag
      - [ ] [Update S3PrefixSensor to support checking multiple prefixes within 
a bucket (#18807)](https://github.com/apache/airflow/pull/18807): @anaynayak
      - [ ] [Move validation of templated input params to run after the context 
init (#19048)](https://github.com/apache/airflow/pull/19048): @eskarimov
      - [ ] [ fix SagemakerProcessingOperator ThrottlingException 
(#19195)](https://github.com/apache/airflow/pull/19195): @ChanglinZhou
      - [ ] [Fix S3ToRedshiftOperator 
(#19358)](https://github.com/apache/airflow/pull/19358): @mariotaddeucci
   
   Thanks to everyone involved in the PRs:
   @eskarimov @blag @anaynayak @Brooke-white @mariotaddeucci @ignaski 
@ChanglinZhou @guotongfei
   
   ### Committer
   
   - [X] I acknowledge that I am a maintainer/committer of the Apache Airflow 
project.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to