-
Notifications
You must be signed in to change notification settings - Fork 113
Encapsulate workflow basic dependencies into a workflow-core package #2942
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
Conversation
bobbai00
left a comment
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.
Left one minor. LGTM!
|
Can other micro services like |
That is the idea. I sent you a POC branch as an example for using workflow-core as dependency. |
…2942) This PR adds a new sub-project in sbt called `workflow-core`, under micro-services. It contains a duplicated codebase of workflow core dependencies, including: - `Tuple`, `Attribute`, `Schema`; - `OperatorExecutor`; - `PhysicalOp`, `PhysicalPlan`; - Identities; - and other utility functions. ### Migration plan: After exporting workflow-core as a local dependency, we can build workflow-compiling-service and workflow-execution-service based on it.
This PR adds a new sub-project in sbt called
workflow-core, under micro-services.It contains a duplicated codebase of workflow core dependencies, including:
Tuple,Attribute,Schema;OperatorExecutor;PhysicalOp,PhysicalPlan;Migration plan:
After exporting workflow-core as a local dependency, we can build workflow-compiling-service and workflow-execution-service based on it.