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

Upgrade to deequ 2.0.4-spark-3.3 dependency #196

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

rdsharma26
Copy link
Contributor

@rdsharma26 rdsharma26 commented Apr 11, 2024

Description of changes:

This commit updates the Spark 3.3 dependency of Deequ. There are some breaking changes to the Scala APIs, from a Py4J perspective. In order to work around that, we use the Spark version to switch between the updated API and the old API. This is not sustainable and will be revisited in a future PR, or via a different release mechanism. The issue is that we have multiple branches for multiple Spark versions in Deequ, but only one branch in PyDeequ.

The changes were verified by running the tests in Docker against Spark version 3.3. The docker file was also updated so that it copies over the pyproject.toml file and installs dependencies in a separate layer, before the code is copied. This allows for fast iteration of the code, without the need to install dependencies every time the docker image is built.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This commit updates the Spark 3.3 dependency of Deequ. There are some breaking changes to the Scala APIs, from a Py4J perspective. In order to work around that, we use the Spark version to switch between the updated API and the old API. This is not sustainable and will be revisited in a future PR, or via a different release mechanism. The issue is that we have multiple branches for multiple Spark versions in Deequ, but only one branch in PyDeequ.

The changes were verified by running the tests in Docker against Spark version 3.3. The docker file was also updated so that it copies over the pyproject.toml file and installs dependencies in a separate layer, before the code is copied. This allows for fast iteration of the code, without the need to install dependencies every time the docker image is built.
@chenliu0831
Copy link
Contributor

Nice - this seems to be a short term solution for #169.

Also would this address the issue we run into for 3.4+ #168?

@rdsharma26
Copy link
Contributor Author

@chenliu0831 #168 will likely not be fixed by this. I'll address the upgrade of Spark 3.4 and the associated changes in a separate PR.

@chenliu0831
Copy link
Contributor

@rdsharma26 got it - I think the title of the PR might be more accurate if it's about "Deequ 2.0.4" parity

@rdsharma26 rdsharma26 changed the title Updated Spark 3.3 dependency Upgrade to deequ-2.0.4-spark3.3 dependency Apr 11, 2024
@rdsharma26 rdsharma26 changed the title Upgrade to deequ-2.0.4-spark3.3 dependency Upgrade to deequ 2.0.4-spark-3.3 dependency Apr 11, 2024
@rdsharma26 rdsharma26 merged commit 59274a5 into awslabs:master Apr 11, 2024
4 checks passed
@rdsharma26 rdsharma26 deleted the upgrade-spark3.3-dep branch April 11, 2024 19:54
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.

2 participants