Skip to content
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

Provide upper bound to great expectations #2717

Merged

Conversation

thomasjpfan
Copy link
Member

Why are the changes needed?

Fixes CI issue with a breaking change in great expectations 1.0.0.

@@ -196,7 +196,7 @@ def to_python_value(
ge_conf = GreatExpectationsFlyteConfig(**conf_dict)

# fetch the data context
context = ge.data_context.DataContext(ge_conf.context_root_dir) # type: ignore
context = ge.get_context(context_root_dir=self._context_root_dir) # type: ignore
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we require greatexpectations>=1.0.0 in setup.py?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eapolinario
eapolinario previously approved these changes Aug 28, 2024
pingsutw
pingsutw previously approved these changes Aug 28, 2024
pingsutw
pingsutw previously approved these changes Aug 28, 2024
wild-endeavor
wild-endeavor previously approved these changes Aug 28, 2024
eapolinario
eapolinario previously approved these changes Aug 28, 2024
@pingsutw
Copy link
Member

The test is still failing

Signed-off-by: Thomas J. Fan <thomasjpfan@gmail.com>
@thomasjpfan thomasjpfan force-pushed the thomasjpfan/fix_great_expectations_ci branch from ee5b96d to 26dcd41 Compare August 28, 2024 18:44
@thomasjpfan thomasjpfan changed the title Support great expectations 1.0.0 API in CI Provide upper bound to great expectations Aug 28, 2024
@eapolinario eapolinario merged commit 2452c74 into flyteorg:master Aug 28, 2024
101 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants