Hi all, Based on some work I've been doing internally, I put together a public version of a design doc template for PTransforms.
https://s.apache.org/ptransform-design-doc A major goal is to be explicit about important questions that make a transform robust: - what are "all" the parameters to a transform? - how could a transform fail? - how could we monitor or measure the transform? - how could we use a transform in a new context like YAML or a new SDK? All of these together add up to a PTransform being a more self-contained piece of software that can be understood and used in novel ways, instead of just defined by the code and behavior that may accrete over time tightly coupled to the SDK it was written with. LMK what you think. Of course, I can't force anyone to use it or not use it, except for my team internal to my employer :-) Kenn
