Skip to content

Async S3 support needed #32174

Closed
Closed

Description

@yjdlau

Description

We need async support for S3 facilities for use in our Triggers.
We see AwsBaseAsyncHook was introduced in this commit (PR 28850) merged on 2023-03-14.

However in #31610 , AwsBaseAsyncHook was marked Deprecated by @pankajastro and subsequently approved by @vincbeck .

I would like to know:

  • on what basis do you determine this class is not used? There has been no discussions in the PR.
  • from a user stance, providing a new functionality then removing it a few months later is not very good practice.
  • is async S3 operations going to be supported ? We have code based on this and deprecating this will break our code.

Many thanks, particularly to the two gentlemen I named above.

Use case/motivation

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. boring-cyborg commented on Jun 27, 2023

    @boring-cyborg

    Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

  2. pankajastro commented on Jun 27, 2023

    @pankajastro
    Member

    We decided to use boto waiter for aws deferrable operator and not create a separate async hook.
    You can check some examples here https://github.com/apache/airflow/tree/main/airflow/providers/amazon/aws/triggers how we are creating triggers. particular line

    async with self.hook.async_conn as client:

  3. yjdlau commented on Jun 27, 2023

    @yjdlau
    Author

    @pankajastro Could you please add context to your PR and discussion, particularly the link to the discussion. From your PR it looks like you're killing a feature without any discussion.

  4. pankajastro commented on Jun 27, 2023

    @pankajastro
    Member

    from a user stance, providing a new functionality then removing it a few months later is not very good practice.

    Right, but keeping duplicate/unused code is not good. When I say unused code I mean not getting used in airflow code. This is a public interface that why I have deprecated it first.

    is async S3 operations going to be supported

    yes, it will be supported.

  5. pankajastro commented on Jun 27, 2023

    @pankajastro
    Member

    @pankajastro Could you please add context to your PR and discussion, particularly the link to the discussion. From your PR it looks like you're killing a feature without any discussion.

    we have a discussion and PR #30032 where we decided to use the waiter and not create a separate hook async operator.

  6. pankajastro commented on Jun 27, 2023

    @pankajastro
    Member

    From your PR it looks like you're killing a feature without any discussion.

    FYI: I added AwsBaseAsyncHook hook

  7. yjdlau commented on Jun 27, 2023

    @yjdlau
    Author

    Got it. That clears things up. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind:featureFeature Requestsneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions