je-ik commented on issue #18479:
URL: https://github.com/apache/beam/issues/18479#issuecomment-3983534648
Hi @MansiSingh17, I was thinking about this and essentially yes, it might be
possible to split the projects, probably something like:
a) design common data objects (probably based on protobuffs) that will be
used for communication between transforms (e.g. watermarks, windwedvalues,
runtime metadata)
b) design (possibly abstract or interface) watermark manager that will be
used in all transforms that need to compute input/output watermarks
c) create a common skeleton of pipeline translator and translation context
This might be enough to split these projects, but Project B will _still_ be
heavily dependent on Project A. Without Project A being successfully merged,
Project B will not be able to succeed. So this is a risk you would probably
have to face.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
