Re: How to write an IO guide draft

2023-01-10 Thread Robert Burke
It's my intent this quarter to translate the document for Go. A document like this has been the main blocker to developing these instructions as I'm adamant about not replicating the initial IO stumbles that any naive author would go through. I'm very excited about this. On Tue, Jan 10, 2023, 8:4

Re: How to write an IO guide draft

2023-01-10 Thread Sachin Agarwal via dev
Totally agreed with that, but it's not bad as a statement of intent for our vision - On Tue, Jan 10, 2023 at 8:34 AM Alexey Romanenko wrote: > I doubt that it will be a "de-facto" standard behaviour for all runners in > the short term until the cross-language funtionality brings additional > com

Re: How to write an IO guide draft

2023-01-10 Thread Alexey Romanenko
I doubt that it will be a "de-facto" standard behaviour for all runners in the short term until the cross-language funtionality brings additional complexity into pipeline deployment and performance overhead. Perhaps, it will be changed in long term, but for now, I may guess that the most of Be

Re: How to write an IO guide draft

2023-01-10 Thread Sachin Agarwal via dev
I think the idea of cross language is that an IO is only in one language and others can use that IO. My feeling is that the idea of “what language is this IO in” becomes an implementation detail that folks won’t have to care about longer term. There are enhancements needed to the expansion service

Re: How to write an IO guide draft

2023-01-10 Thread Austin Bennett
This is great, thanks for putting this together! A related question: are we as a community targeting java to be the canonical/target IO language if an IO does not currently exist? If that is not the case, then I would imagine we are hoping that we might eventually also wind up with good examples

Re: How to write an IO guide draft

2023-01-10 Thread Herman Mak via dev
Thanks John! Herman Mak | Customer Engineer, Hong Kong, Google Cloud | herman...@google.com | +852-3923-5417 On Tue, Jan 10, 2023 at 12:58 AM John Casey via dev wrote: > Hi All, > > I spent the last few weeks of December drafting a "How to write an IO > guide": > https://docs.google.com/d

How to write an IO guide draft

2023-01-09 Thread John Casey via dev
Hi All, I spent the last few weeks of December drafting a "How to write an IO guide": https://docs.google.com/document/d/1-WxZTNu9RrLhh5O7Dl5PbnKqz3e5gm1x3gDBBhszVF8/edit# and an associated code sample: https://github.com/apache/beam/pull/24799 My goal is to make it easier for a new IO developer