-
Notifications
You must be signed in to change notification settings - Fork 303
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
Fix a bug in gx integration #1675
Fix a bug in gx integration #1675
Conversation
Signed-off-by: Xin Shi <[email protected]>
Signed-off-by: Xin Shi <[email protected]>
Thank you for opening this pull request! 🙌 These tips will help get your PR across the finish line:
|
Codecov Report
@@ Coverage Diff @@
## master #1675 +/- ##
==========================================
+ Coverage 71.00% 71.03% +0.02%
==========================================
Files 336 336
Lines 30781 30798 +17
Branches 5576 5589 +13
==========================================
+ Hits 21855 21876 +21
+ Misses 8379 8375 -4
Partials 547 547 |
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.
@XinEDprob test is failing, mind taking a look
@pingsutw thanks for letting me know. Will take a look at the test and finish the corresponding change in this week. |
Signed-off-by: Xin Shi <[email protected]>
Signed-off-by: Xin Shi <[email protected]>
plugins/flytekit-greatexpectations/flytekitplugins/great_expectations/task.py
Outdated
Show resolved
Hide resolved
Signed-off-by: Xin Shi <[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.
Signed-off-by: Xin Shi <[email protected]>
@pingsutw do you have any insights about why there is an error in the test? I do not think my changes may affect that part. |
@XinEDprob nvm, that's a flaky test. merged it |
Congrats on merging your first pull request! 🎉 |
TL;DR
Fixed a bug in the integration of Flyte and Great Expectations. Without this fix, pyspark dataframe will always be converted to pandas dataframe in Great Expectations. As a result, there will have an error when people want to use
SparkDFExecutionEngine
.Type
Are all requirements met?
Complete description
I use
selected_datasource[0]["execution_engine"]["class_name"]
to recognize theexecution_engine
declared by the user for Great Expectations. If it is aSparkDFExecutionEngine
, the data which is in the form FlyteSchema is converted topyspark.sql.dataframe.DataFrame
, else transform the data to the defaultpandas.dataframe
.Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA