This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Factor out the streaming SQL transformations into a dedicated Processor #20
Assignees
Labels
Comments
tzolov
added
documentation
tzolov
added a commit
that referenced
this issue
Jun 8, 2022
- Split the Processor semantics into 3 general purpose processor types - Time Window Aggregation type - existing multi-binder + sidecar UDF (no SQL anymore) - FSQL type - factor out the existing streaming SQL into dedicated processor type which is deployed in a separate POD. - SCS type - Spring Cloud Stream support including all OOTB SCDF apps. - Update the Processor CRD to reflect the new Processor semantics. - Refactor the Processor K8s Controller the allow configuring and deploying the above 3 processor types. - Samples - refactor all samples to reflect the new Processor(s) semantics. - added SCS sample - Docs - update samples docs - new SCS sample doc - add Stream Schema page - add architecture sub-section - basic SR concepts info added to the Usage section Resolves #20
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Existing Processor semantics bundles together 2 presumably unrelated tasks (SQL + UDF) under the same executable entity (Pod) though both tasks have different development and run-time concerns.
To address this we need allow support different types of processor types While using the same Processor CRD resource the controller should distinct and deploy the processor in accordance of its type.
The text was updated successfully, but these errors were encountered: