-
Notifications
You must be signed in to change notification settings - Fork 305
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
Introducing whylogs integration to flytekit #1104
Introducing whylogs integration to flytekit #1104
Conversation
* Details: It creates a schema for "transforming" whylogs' DatasetProfileView objects to and from the FlyteSchema. This PR also creates two renderers with FlyteDeck, one for the Constraints report and the other for the SummaryDriftReport. Signed-off-by: murilommen <[email protected]>
changes: breaking down single test_schema.py unit test into test_schema + test_renderer, each with their own concerns Signed-off-by: murilommen <[email protected]>
details: removing extra lines later caught by flake8 Signed-off-by: murilommen <[email protected]>
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.
This looks good, let's just ensure the tests you added run in CI. In order to do that, can you add the new plugin to this list?
Signed-off-by: murilommen <[email protected]>
this looks good. do you think you'll be able to add an example to https://github.com/flyteorg/flytesnacks/tree/master/cookbook/integrations/flytekit_plugins as well please? |
Codecov Report
@@ Coverage Diff @@
## master #1104 +/- ##
==========================================
+ Coverage 86.91% 86.93% +0.01%
==========================================
Files 275 275
Lines 25435 25448 +13
Branches 2506 2862 +356
==========================================
+ Hits 22108 22123 +15
+ Misses 2851 2847 -4
- Partials 476 478 +2
Continue to review full report at Codecov.
|
Signed-off-by: murilommen <[email protected]>
Signed-off-by: murilommen <[email protected]>
e4104bd
to
1475a85
Compare
It looks like version
|
We talked offline and this has to do with whylogs only supporting python versions < 3.10. Update coming shortly. |
Signed-off-by: murilommen <[email protected]>
details: whylogs require protobuf > 3.15, but flyteidl can't handle protobuf < 4.0, so adding it as a restriction to setup.py Signed-off-by: murilommen <[email protected]>
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.
Make sure to run make fmt
from the root of the repo.
details: ran black command on the plugin implementation and caught something with black Signed-off-by: murilommen <[email protected]>
Signed-off-by: murilommen <[email protected]>
b62c81d
to
e7763a4
Compare
Congrats on merging your first pull request! 🎉 |
* Introducing whylogs integration to flytekit * Details: It creates a schema for "transforming" whylogs' DatasetProfileView objects to and from the FlyteSchema. This PR also creates two renderers with FlyteDeck, one for the Constraints report and the other for the SummaryDriftReport. Signed-off-by: murilommen <[email protected]> * refactoring tests changes: breaking down single test_schema.py unit test into test_schema + test_renderer, each with their own concerns Signed-off-by: murilommen <[email protected]> * styleguide fixes details: removing extra lines later caught by flake8 Signed-off-by: murilommen <[email protected]> * add plugin to ci checks Signed-off-by: murilommen <[email protected]> * adding requirements files + lint fixes Signed-off-by: murilommen <[email protected]> * removing entrypoints from setup.py Signed-off-by: murilommen <[email protected]> * adding a python 3.10 build restriction Signed-off-by: murilommen <[email protected]> * fixing protobuf's version to < 4 details: whylogs require protobuf > 3.15, but flyteidl can't handle protobuf < 4.0, so adding it as a restriction to setup.py Signed-off-by: murilommen <[email protected]> * lint setup.py details: ran black command on the plugin implementation and caught something with black Signed-off-by: murilommen <[email protected]> * fixing comma on setup.py Signed-off-by: murilommen <[email protected]>
* Introducing whylogs integration to flytekit * Details: It creates a schema for "transforming" whylogs' DatasetProfileView objects to and from the FlyteSchema. This PR also creates two renderers with FlyteDeck, one for the Constraints report and the other for the SummaryDriftReport. Signed-off-by: murilommen <[email protected]> * refactoring tests changes: breaking down single test_schema.py unit test into test_schema + test_renderer, each with their own concerns Signed-off-by: murilommen <[email protected]> * styleguide fixes details: removing extra lines later caught by flake8 Signed-off-by: murilommen <[email protected]> * add plugin to ci checks Signed-off-by: murilommen <[email protected]> * adding requirements files + lint fixes Signed-off-by: murilommen <[email protected]> * removing entrypoints from setup.py Signed-off-by: murilommen <[email protected]> * adding a python 3.10 build restriction Signed-off-by: murilommen <[email protected]> * fixing protobuf's version to < 4 details: whylogs require protobuf > 3.15, but flyteidl can't handle protobuf < 4.0, so adding it as a restriction to setup.py Signed-off-by: murilommen <[email protected]> * lint setup.py details: ran black command on the plugin implementation and caught something with black Signed-off-by: murilommen <[email protected]> * fixing comma on setup.py Signed-off-by: murilommen <[email protected]>
TL;DR
Whylogs plugin integration
Type
Are all requirements met?
Complete description
It creates a schema for "transforming" whylogs' DatasetProfileView objects to and from the FlyteSchema. This PR also creates two renderers, one for whylogs' Constraints report and the other for the SummaryDrift Report.
Tracking Issue
NA
Follow-up issue
NA