I've never published npm artifacts before, but I imagine the hardest part
is getting the credentials set up, then it is probably very easy to set up
a GitHub Actions workflow to publish
Hi Beam Devs,
Calling out it looks like our release process for apache-beam for
typescript/npm is broken, seemingly the last published release was 2.49.0
about 9 months ago. The other languages look like they are publishing to
expected locations.
https://www.npmjs.com/package/apache-beam
I
Correct, I've just been pushing these manually, and lately there haven't
been many changes to push. I'm all for getting these set up as part of the
standard release process.
On Tue, Apr 16, 2024 at 1:22 PM Danny McCormick
wrote:
> I've never published npm artifacts before, but I imagine the
Yes, but that's inevitable as stateful ParDo in a sense live outside of
most of the window/trigger semantics. Basically a stateful ParDo is the
user executing low-level control over these semantics, and controlling
output frequency themselves with timers. One could however still propagate
the
On 4/11/24 18:20, Reuven Lax via dev wrote:
I'm not sure it would require all that. A "basic" implementation could
be done on top of our existing model. Essentially the user
would specify triggers at the sink ParDos, then the runner would walk
backwards up the graph, reverse-propagating these
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/30966 The PreCommit
Thank you Reuven for the response!
I'll update the design doc to include adding support for the generic
classes. As for the new reflection API that's what I propose in the doc as
well, it seems like the right choice.
By codegen path you mean using bytebuddy to generate the constructor and
the
