-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
move basic normalization to connectors_base build #7068
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
f8c7e2a
move basic normalization to connectors_base build
cgardens 1778689
remove normalization from platform build
cgardens e43436d
move normalization builds to normalization package
cgardens 30cd43e
fix relative path
cgardens 2951272
revert to pinned versions of normalization
cgardens 6a1e853
fix paths
cgardens 61f5141
fix latest build; update image checker to check for normalization
cgardens 7472354
copy
cgardens 6035728
pull normalization image version from java sourceg
cgardens 4f5b7ff
bump normalization version; restore tests
cgardens 7429a6f
Merge branch 'master' into cgardens/move_normalization_to_conn_build
cgardens File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
31 changes: 31 additions & 0 deletions
31
airbyte-integrations/bases/base-normalization/docker-compose.build.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
version: "3.7" | ||
|
||
services: | ||
normalization: | ||
image: airbyte/normalization:${VERSION} | ||
build: | ||
dockerfile: Dockerfile | ||
context: . | ||
labels: | ||
io.airbyte.git-revision: ${GIT_REVISION} | ||
normalization-mssql: | ||
image: airbyte/normalization-mssql:${VERSION} | ||
build: | ||
dockerfile: mssql.Dockerfile | ||
context: . | ||
labels: | ||
io.airbyte.git-revision: ${GIT_REVISION} | ||
normalization-mysql: | ||
image: airbyte/normalization-mysql:${VERSION} | ||
build: | ||
dockerfile: mysql.Dockerfile | ||
context: . | ||
labels: | ||
io.airbyte.git-revision: ${GIT_REVISION} | ||
normalization-oracle: | ||
image: airbyte/normalization-oracle:${VERSION} | ||
build: | ||
dockerfile: oracle.Dockerfile | ||
context: . | ||
labels: | ||
io.airbyte.git-revision: ${GIT_REVISION} |
12 changes: 12 additions & 0 deletions
12
airbyte-integrations/bases/base-normalization/docker-compose.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
version: "3.7" | ||
|
||
# this file only exists so that we can easily check that all of these images exist in docker hub in check_images_exist.sh | ||
services: | ||
normalization: | ||
image: airbyte/normalization:${VERSION} | ||
normalization-mssql: | ||
image: airbyte/normalization-mssql:${VERSION} | ||
normalization-mysql: | ||
image: airbyte/normalization-mysql:${VERSION} | ||
normalization-oracle: | ||
image: airbyte/normalization-oracle:${VERSION} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@ChristopheDuong why were these added here?
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.
Since it is not possible to “edit” and choose what normalization version you want like you can with connectors, I switched normalization version tags to follow airbyte core versions instead as discussed in this thread (I also discussed it with people separately and overall people were supportive of the switch) https://airbytehq.slack.com/archives/C019WEENQRM/p1633710746415900
See also comment making it part of composeBuild: #2054 (comment)
Overall it’d make it easier to publish new normalization images (when releasing airbyte) instead of doing it whenever a PR is merged…. (the docker image is not useable until there is a release of airbyte anyway)
And now that we have multiple docker images for normalization to publish, we'd have to include them in the
docker-compose-build.yaml
to make them as part of airbyte release?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.
We could revert back but then we need to adapt the publish script and the
DefaultNormalizationRunnerFactory
tooThere 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 a good way forward is to split normalisation out to use it's own versioning and inject this version by env var.
After this we split the builds so normalisation is a separate build from the platform. In this sense, we have 3 build paths 1) connectors 2) normalisation 3) platform. This will allow the platform team to remove Python from our/their deps.
To simplify things, we can continue to release normalisation with the current OSS release. We can also continue to pin to the Airbyte version. There is some unnecessary work, but it's mostly automated so no sweat off our backs.
We can also start with a single global normalisation version. We can add individual connector normalisation versions as we run into those cases.
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.
For now, I'm reverting back to how we had it that normalization has its own version that is de coupled from platform. I think the next thing to figure out is how we want to package normalization in the future. It seems like either packaging mysql normalization in the mysql destination container or at least having that container specify the name of the container that should be used to normalize it seem like 2 reasonable paths forward but those are just idea, open to others.