-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for FTP as file location #1482
Conversation
Codecov ReportBase: 97.43% // Head: 93.16% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1482 +/- ##
==========================================
- Coverage 97.43% 93.16% -4.27%
==========================================
Files 21 65 +44
Lines 740 3481 +2741
Branches 0 418 +418
==========================================
+ Hits 721 3243 +2522
- Misses 19 157 +138
- Partials 0 81 +81 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I think we should also support export_file() operator. |
@rajaths010494 there should be tests for export file as well which are required to be added for FTP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you planing to add some integration tests also?
3c8702d
to
65cdae4
Compare
added integration test case for export and read the content and assert it |
FTP support file location
6594840
to
5b23a9f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
relates-to #969 **Please describe the feature you'd like to see** It is a very common ETL operation to either push data to or load data from FTP sources **Describe the solution you'd like** FTP should be valid location types in `File` **Are there any alternatives to this feature?** Implementors otherwise need to use workarounds like `S3toSFTPOperator` **Acceptance Criteria** - [x] All checks and tests in the CI should pass - [x] Unit tests (90% code coverage or more, [once available](#191)) - [x] Integration tests (if the feature relates to a new database or external service) - [x] Example DAG - [x] Docstrings in [reStructuredText](https://peps.python.org/pep-0287/) for each of methods, classes, functions and module-level attributes (including Example DAG on how it should be used) - [x] Exception handling in case of errors - [x] Logging (are we exposing useful information to the user? e.g. source and destination) - [x] Improve the documentation (README, Sphinx, and any other relevant) - [x] How to use Guide for the feature ([example](https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/operators/postgres_operator_howto_guide.html))
relates-to #969
Please describe the feature you'd like to see
It is a very common ETL operation to either push data to or load data from FTP sources
Describe the solution you'd like
FTP should be valid location types in
File
Are there any alternatives to this feature?
Implementors otherwise need to use workarounds like
S3toSFTPOperator
Acceptance Criteria