Hi
I can do that today if there's no other PMC available.
Regards
JB
On Thu, Jun 1, 2023 at 2:02 AM Ritesh Ghorse via dev
wrote:
>
> Could a PMC member help with the PMC-only finalization steps for 2.48.0 [1]?
> Specifically:
>
> - Deploy source release to dist.apache.org
> - Recordkeeping wit
Could a PMC member help with the PMC-only finalization steps for 2.48.0
[1]? Specifically:
- Deploy source release to dist.apache.org
- Recordkeeping with ASF
Once those steps are done all that's left is to promote the release [2].
Thank you!
[1] https://beam.apache.org/contribute/release-guide
chamikaramj merged PR #645:
URL: https://github.com/apache/beam-site/pull/645
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@beam.apach
chamikaramj commented on PR #645:
URL: https://github.com/apache/beam-site/pull/645#issuecomment-1571110027
LGTM
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscr
riteshghorse commented on PR #645:
URL: https://github.com/apache/beam-site/pull/645#issuecomment-1571108588
R: @jrmccluskey @chamikaramj
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the spec
Completely forgot to circle back to this, these should published now
On Wed, May 31, 2023 at 11:10 AM Jack McCluskey
wrote:
> I'll get that going shortly.
>
> On Wed, May 31, 2023 at 11:00 AM Ritesh Ghorse via dev <
> dev@beam.apache.org> wrote:
>
>> Could someone from the `beammaintainers Docke
1. Yes, using state is a better fit than Beam windowing. You will want to
use the new feature of annotating the DoFn with @RequiresTimeSortedInput.
This will make it so you can be sure you are actually getting the
"previous" event. They can arrive in any order without this annotation. You
won't be
Hi Kenn,
Thanks for clarification.
1. Just to put an example in front - for every event that comes in I
need to find corresponding previous event of same user_id and pass
previous_event_timestamp in the current event payload down (and also
current event becomes previous event for future event
I'll get that going shortly.
On Wed, May 31, 2023 at 11:00 AM Ritesh Ghorse via dev
wrote:
> Could someone from the `beammaintainers DockerHub team` please help deploy
> the docker images for release [1]
>
> Thanks!
>
> [1]
> https://beam.apache.org/contribute/release-guide/#9-prepare-documents:
Could someone from the `beammaintainers DockerHub team` please help deploy
the docker images for release [1]
Thanks!
[1]
https://beam.apache.org/contribute/release-guide/#9-prepare-documents:~:text=to%20be%20uploaded.)-,Deploy%20docker%20images%20to%20DockerHub,-Note%3A%20if%20you
On Wed, May 31
I'm happy to announce that we have unanimously approved this release.
There are 7 approving votes, 5 of which are binding:
* Alexey Romanenko
* Ahmet Altay
* Reuven Lax
* Robert Bradshaw
* Chamikara Jayalath
Thank you to the following non-binding voters for helping with validation:
* Bruno Volpat
+1 (non-binding) (Python)
Svetak Sundhar
Data Engineer
s vetaksund...@google.com
On Wed, May 31, 2023 at 1:50 AM Chamikara Jayalath via dev <
dev@beam.apache.org> wrote:
> Nvm, I was running the Kafka cluster and the job in two different
> projects. It's working as expected.
>
> +1 (bindin
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/26911 [Bug]: UNNEST ARRAY
13 matches
Mail list logo
