It seems like we keep running into translation issues with XLang due to how
it is represented in the SDK. (e.g. Brian's work on context map due to loss
of coder ids, Heejong's work related to missing environment ids on
windowing strategies).

I understand that there is an effort that is Dataflow specific where the
conversion of the Beam proto -> Dataflow API (v1b3) will help with some
issues but it still requires the SDK pipeline representation -> Beam proto
to occur correctly which won't be fixed by the Dataflow specific effort.

Why did we go with the current approach?

What other ways could we do this?

Reply via email to