I validated python quick starts (direct, dataflow) X (batch, streaming). I
ran into an issue with the dataflow batch case, running the wordcount with
the standard:
python -m apache_beam.examples.wordcount \
--output \
--staging_location \
--temp_location \
--runner DataflowRunner \
--job_name wo
Sounds great. And let's vote and get 2.44.0 out before then just to not fry
my brain with too many threads :-)
On Tue, Jan 10, 2023 at 10:16 AM John Casey via dev
wrote:
> Hi All,
>
> I propose we cut 2.45 on January 18, and I nominate myself as the release
> manager.
> This is a week delayed fr
I have published a new maven staging repository:
https://repository.apache.org/content/repositories/orgapachebeam-1290/
It looks like it has everything, though I did not automate a check. At
least there were no errors during publish which I ran with --no-parallel
overnight, and some specific thing
Hi All,
I propose we cut 2.45 on January 18, and I nominate myself as the release
manager.
This is a week delayed from the Jan 11 schedule, but this would give the
2.44 release time to finish its processes, allowing 2.45 to pick up any
fixes in the 2.44 release.
Thanks,
John
Thanks! Moving my DoFn into a new module worked, and that solved the
slowness as well.
I tried importing it in setup() as well, but that didn't work.
On Fri, Jan 6, 2023 at 2:25 PM Luke Cwik wrote:
> The proto (java) -> bytes -> proto (python) sounds good.
>
> Have you tried moving your DoFn out
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
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
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
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
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
On Wed, Dec 28, 2022 at 7:25 PM Byron Ellis via dev
wrote:
> Thanks for the tips, folks! Took a bit of doing, but I got Java -> Python
> -> Java working without Docker being involved in the process (getting it
> working with Docker being involved wasn't so bad... though it didn't do
> what I want
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
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/24776 [Bug]: Race conditi
13 matches
Mail list logo
