Thank you, Yi!
On Wed, Jul 16, 2025 at 5:02 PM Ahmed Abualsaud via dev
wrote:
> Amazing, thank you Yi!
>
> On Wed, Jul 16, 2025 at 4:59 PM Yi Hu via dev wrote:
>
>> Hi Beam Developers,
>>
>> As part of Java8 deprecation [1], Beam repo now requires Java11+ to build
>> jars from Beam repository s
Amazing, thank you Yi!
On Wed, Jul 16, 2025 at 4:59 PM Yi Hu via dev wrote:
> Hi Beam Developers,
>
> As part of Java8 deprecation [1], Beam repo now requires Java11+ to build
> jars from Beam repository sources.
>
> * What's affected:
>
> Commit [2] upgraded certain Gradle plugins that dropped
Hi Beam Developers,
As part of Java8 deprecation [1], Beam repo now requires Java11+ to build
jars from Beam repository sources.
* What's affected:
Commit [2] upgraded certain Gradle plugins that dropped Java 8 support. As
a result, build Beam using Gradle now requires Java11+ in JAVA_HOME or PA
It looks like the intro stripped somehow. Here is the full email :)
[Proposal][GSoC 2025] Milvus Vector Sink I/O Connector for Beam
Hello Beam Dev Community,
I'm happy to share the design document for the Milvus Vector Sink I/O
Connector for Apache Beam, developed as part of my GSoC 2025 project
Hello Beam Dev Community,
This sink I/O connector will enable both streaming and batch pipelines to
persist vector embeddings and metadata into Milvus collections.
This sink I/O connector introduces support for writing vector embeddings
and associated metadata from both streaming and batch pipeli
Thank you!
On Wed, Jul 16, 2025 at 3:13 PM Vitaly Terentyev via dev <
dev@beam.apache.org> wrote:
> Hello everyone,
>
> The next release (2.67.0) branch cut is scheduled for July 23, 2025, 1
> week from today, according to the release calendar [1]. I'd like to
> perform this release; I will cut t
Hello everyone,
The next release (2.67.0) branch cut is scheduled for July 23, 2025, 1
week from today, according to the release calendar [1]. I'd like to
perform this release; I will cut the branch on that date, and cherry-pick
release-blocking fixes afterwards, if any.
Please help with the rele
On Wed, Jul 16, 2025 at 4:51 AM Joey Tran wrote:
>
>
> On Wed, Jul 16, 2025 at 2:24 AM Chamikara Jayalath via dev <
> dev@beam.apache.org> wrote:
>
>>
>>
>> On Tue, Jul 15, 2025 at 5:32 PM Joey Tran
>> wrote:
>>
>>> "Environment" has become almost-but-not-quite assumed to be a docker
contai
> My two cents: I think it's valuable for explicit type hints to
> override implicit ones for a couple of reasons:
>
> - If there's a bug in inference, at least there's a way to override that.
>
We could still allow a way to force an override e.g.
`Map(extract_z).with_output_types(int, force=True)`
My two cents: I think it's valuable for explicit type hints to
override implicit ones for a couple of reasons:
- If there's a bug in inference, at least there's a way to override that.
- Explicit type hints can better capture intent. E.g. in the above
example, one might type the output to be of ty
Hey Joey,
I have a few concerns around creating a more variable approach to
determining types. On the SDK side we'd be trying to pull hints from each
route and then doing some comparison across each individual component of
the hint to determine which is the most narrow. For the simplest case,
wher
On Wed, Jul 16, 2025 at 2:24 AM Chamikara Jayalath via dev <
dev@beam.apache.org> wrote:
>
>
> On Tue, Jul 15, 2025 at 5:32 PM Joey Tran
> wrote:
>
>> "Environment" has become almost-but-not-quite assumed to be a docker
>>> container image specification. TBH I haven't dug in deeply recently but
>
12 matches
Mail list logo
