AlexisBRENON opened a new pull request, #33578:
URL: https://github.com/apache/airflow/pull/33578
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
Related: #8804, #3526
As explained in the related issue, it can be hard to cover all the
<provider>To<provider> use cases. It could be nice to have a generic "file
transfer" operator which can handle most of the storage provider (local
filesystem as well as cloud blob storages). Such kind of storage wrapper
already exists as the `fsspec` library which is already an Airflow dependency.
This PR aims at providing a base "class" (it's more like a mixin) to mix
with blob storage provider (such as S3, GCS, etc.) to allow easy creation of
fsspec.FileSystem from such hooks.
I am not very fluent with the Hook/Connection API, so I am not sure that
this PR make sense.
---
--
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]
