-
Notifications
You must be signed in to change notification settings - Fork 914
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
Make Kedro compatible with Airflow 2.4.2 #2030
Conversation
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
Thanks for the PR. Since airflow isn't a core dependency of Kedro, I think it is ok to lift the upper bound to make it compatible with airflow, but at the same time we should keep the lower bound. There could be some other libraries pinned a lower version and kedro should allow that. What do you think? |
@noklam I thought about using attrs >=21.3,<23.0 ; but looking at the limited Kedro code dependency and usage of attrs ; and assuming Airflow compatibility was more important - I went with >=22.1.0,<23.0. But thinking through it a bit more, you have a good point - Pinning the lower bound of attrs so high, will actually break compatibility with older versions of airflow (e.g. airflow 2.2) I think a better pin will be attrs >=20.0,<23.0 - which will give us backward compatibility to Airflow 2.0 & Airflow 1.X ; from the time attrs was introduced as an airflow dependency. Let me give that a shot - attrs >=20.0,<23.0 |
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
@rxm7706 See the release note of |
attrs>=20.0, <23.0 # The minimum version required for Airflow 2 is >=20.0 and Airflow 2.4.2 is >=22.1 Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
@noklam Is it odd that only one set to tests failed - Just E2E Windows and Python ; and it seems to be a connection time out while launching a notebook, Attrs bounds itself don't seem to have caused any failures Is there a way to rerun the CI suite ? Without a resorting to a PR just to trigger it. |
@rxm7706 The only reason it works is that it is installing the latest version. If you want to test the lower bound, you need to pin See this screenshot from the CI, and check out the I suggest keeping the |
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
Rxm7706 patch 2 Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com>
@noklam changes made as suggested attrs>=21.3, <23.0 |
@rxm7706 Thank you :) I have re-trigger the CI pipeline, let's see if it works. It fails occasionally and that may be a CircleCI issue. |
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.
Thanks for the PR! Looks good overall, but left a couple small comments and thoughts.
Also, can you shorten the PR title a bit, please? :) Maybe just drop the part after the hyphen.
dependency/requirements.txt
Outdated
@@ -1,5 +1,5 @@ | |||
anyconfig~=0.10.0 | |||
attrs~=21.3 | |||
attrs>=21.3, <23.0 # The minimum version required for Airflow 2 is >=20.0 and Airflow 2.4.2 is >=22.1 |
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.
Maybe we shouldn't have an upper bound? https://www.attrs.org/en/22.1.0/changelog.html?highlight=upgrade#changelog They have a very strong backward-compatibility policy.
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.
Also, I'm not sure if we need to explain Airflow bounds here; the 21.3 is a Kedro-based lower bound, and we should just strive to be generally loose beyond that.
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.
I think it's ok to remove the upper bound since I don't remember attrs
have ever created a problem for us. Though technically it wouldn't matter too much since it's a CalVer release.
Co-authored-by: Deepyaman Datta <deepyaman.datta@utexas.edu>
@rxm7706 The DCO is failing, would you be able to fix it? I removed the upper bound, it should be fine unless the tests tell otherwise. |
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.
Signed-off-by: rxm7706
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.
Signed-off-by: rxm7706
@noklam I can't seem to fix the DCO - which is a strange fail, because I used the github UI to approve & make the change - If you cant fix it, just let me know - might just close this PR and do a new one |
This commit adds a video dataset that can read and write video files. The dataset is backed by OpenCVs video reader and writer and different buffer protocols such as PIL.Image and numpy.ndarray. There is one class for iterables (e.g. list of frames) and one for generators. Since large videos might not fit in memory, this ability allows us to read one frame from the video file, transform the frame and write it to another video file. Thus there is only need for one frame at a time in memory. The different codecs that are supported depends on the codecs installed and how OpenCV was compiled. Signed-off-by: Daniel Falk <daniel.falk.1@fixedit.ai> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Updates the requirements on [fsspec](https://github.com/fsspec/filesystem_spec) to permit the latest version. - [Release notes](https://github.com/fsspec/filesystem_spec/releases) - [Commits](fsspec/filesystem_spec@2021.04.0...2022.11.0) --- updated-dependencies: - dependency-name: fsspec dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Updates the requirements on [pip-tools](https://github.com/jazzband/pip-tools) to permit the latest version. - [Release notes](https://github.com/jazzband/pip-tools/releases) - [Changelog](https://github.com/jazzband/pip-tools/blob/master/CHANGELOG.md) - [Commits](jazzband/pip-tools@6.9.0...6.10.0) --- updated-dependencies: - dependency-name: pip-tools dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
* Add execution_options to SQLQueryDataSet Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> * Update RELEASE.md Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> * Fix lint issues Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> * Add a check in the unit test Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> * Add test for connection reuse behaviour Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> * Inject execution_options at load time Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> * enhance doc and fix incorrect example Signed-off-by: Nok <nok_lam_chan@mckinsey.com> * More docs change Signed-off-by: Nok <nok_lam_chan@mckinsey.com> * Fixing typos Signed-off-by: Nok <nok_lam_chan@mckinsey.com> Signed-off-by: Clotilde Guinard <clotilde_guinard@hotmail.fr> Signed-off-by: Nok <nok_lam_chan@mckinsey.com> Co-authored-by: Nok <nok_lam_chan@mckinsey.com> Co-authored-by: Nok Lam Chan <mediumnok@gmail.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: rxm7706 <95496360+rxm7706@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
* Add SVMLight DataSet Add DataSet for svmlight/libsvm files using scikit-learn library as backend. Resolves #1972 Signed-off-by: Kirill Korotkov <korotkovkm@gmail.com> * Pin scikit-learn version to work with python 3.7 Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> * Update dataset docstring Co-authored-by: Merel Theisen <49397448+merelcht@users.noreply.github.com> * Pin requirements to work with python 3.7 Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> * Add requirements to setup.py Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> * Add changes to dataset docstring Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> * Dummy commit to retrigger CI pt1 Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> * Dummy commit to retrigger CI pt2 Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> * Update dataset dockstring Signed-off-by: Kirill Korotkov <korotkovkm@gmail.com> Signed-off-by: Kirill Korotkov <korotkovkm@gmail.com> Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com> Co-authored-by: Ahdra Merali <90615669+AhdraMeraliQB@users.noreply.github.com> Co-authored-by: Ahdra Merali <ahdra.merali@quantumblack.com> Co-authored-by: Merel Theisen <49397448+merelcht@users.noreply.github.com> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Co-authored-by: Deepyaman Datta <deepyaman.datta@utexas.edu> Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
* Revised the Introduction to make it short and sweet. * Revised the Get Started section. Gone is "Hello Kedro". Gone are the installation pre-requisites (that's just part of the Install Kedro page now). Gone is the "Standalone use of the data catalog - woot woot" and GONE is the page on Kedro starters. * Reordered the create project material to put the project structure breakdown in the section that introduces key concepts and shorten the Iris tutorial to the bare minimum. I did add visualisation at this point though, to highlight Kedro Viz, as I felt it was coming far too late in the spaceflights tutorial and needed to be more prominent as a feature. * Added a TL;DR page to Get Started which some people could probably just use as-is and ignore the rest of the section. * Starters material has moved into a new section all about "Kedro project setup". Much of that section still needs review/revision but I have updated the Starters page so it reads more clearly. * Improved the Kedro-Viz page somewhat (still more to come for Plotly) * Notebooks/IPython materials now merged and simplified Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Signed-off-by: Nok <nok_lam_chan@mckinsey.com>
Description
To Make Kedro Compatible with Airflow 2.4.2
kedro-org/kedro-plugins#73
Development notes
Updates the requirements on attrs to permit the latest version.
Changed dependency/requirements.txt
From attrs~=21.3 to attrs >=22.1.0,<23.0
Development notes
Checklist
RELEASE.md
file