Could you explain the process you used to produce these artifacts?
On Thu, Jan 18, 2024 at 11:23 AM Kenneth Knowles wrote:
> +1
>
> On Wed, Jan 17, 2024 at 6:03 PM Yi Hu via dev wrote:
>
>> Hi everyone,
>>
>>
>> Please review the release of the following artifacts that we vendor:
>>
>> *
+1
On Wed, Jan 17, 2024 at 6:03 PM Yi Hu via dev wrote:
> Hi everyone,
>
>
> Please review the release of the following artifacts that we vendor:
>
> * beam-vendor-grpc-1_60_1
>
>
> Please review and vote on the release candidate #1 for the version 0.1, as
> follows:
>
> [ ] +1, Approve the
I agree that variable support across Runners does limit the adoption of a
feature. But it's also then limited if the SDKs and their local / direct
runners don't yet support the feature. The Go SDK doesn't currently have a way
of specifying that annotation, preventing use. (The lack of mention
Hi,
recently I came across the fact that most runners do not support
@RequiresTimeSortedInput annotation for sorting per-key data by event
timestamp [1]. Actually, runners supporting it seem to be Direct java,
Flink and Dataflow batch (as it is a noop there). The annotation has
use-cases in
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/29972 [Bug]:
