chore: rename project to sghi-etl-core
#2
Merged
Conversation
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
After further RnD, it's now clear it is possible to have the same abstractions for both simpler and complex ETL workflows. Complex workflows in this context refer to ETL workflows that support streaming and batching. Therefore, one API specifications project is sufficient to handle both use cases. Hence, the renaming of the project to a more generic name to emphasize that this is a general API for describing ETL workflows.
kennedykori
force-pushed
the
chore-rename-project
branch
from
584a010
to
0609b0b
Compare
kennedykori
added a commit
that referenced
this pull request
Mar 21, 2024
## [1.0.0-rc.1](...v1.0.0-rc.1) (2024-03-21) ### Dependency Updates * **deps:** update project dependencies ([#3](#3)) ([f1a1ac3](f1a1ac3)) ### Features * add core interfaces ([#1](#1)) ([863929b](863929b)) ### hidden * improve exisiting tests ([#5](#5)) ([ae09099](ae09099)) ### Refactors * rename project to `sghi-etl-core` ([#2](#2)) ([908ed3c](908ed3c))
|
🎉 This PR is included in version 1.0.0-rc.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After further RnD, it's now clear it is possible to have the same abstractions for both simpler and complex ETL workflows. Complex workflows in this context refer to ETL workflows that support streaming and batching. Therefore, one API specifications project is sufficient to handle both use cases. Hence, the renaming of the project to a more generic name to emphasize that this is a general API for describing ETL workflows.