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/22440 [Bug]: Python Batch
Hi, we developed a new IO connector named DataLakeIO, to connect Beam and data
lake, such as Delta Lake, Apache Hudi, Apache iceberg. Beam can use DataLakeIO
to read data from data lake, and write data to data lake. We did not find data
lake IO on https://beam.apache.org/documentation/io/built-
This is wonderful to hear -
https://beam.apache.org/contribute/get-started-contributing/#contribute-code
has the process to contribute; we're very much looking forward to seeing
your DataLakeIO!
On Fri, Aug 5, 2022 at 9:02 AM 张涛 wrote:
>
> Hi, we developed a new IO connector named DataLakeIO, to
Thanks Cham! I really like the proposal, I left a few comments. I also had
one higher-level point I wanted to elevate here:
> Pipeline SDKs can generate user-friendly stub-APIs based on transforms
registered with an expansion service, eliminating the need to develop
language-specific wrappers.
Thi
On Fri, Aug 5, 2022 at 9:44 AM Brian Hulette wrote:
> Thanks Cham! I really like the proposal, I left a few comments. I also had
> one higher-level point I wanted to elevate here:
>
> > Pipeline SDKs can generate user-friendly stub-APIs based on transforms
> registered with an expansion service,
Kiley, do we still have the same blockers? Do you need any help?
On Thu, Aug 4, 2022 at 12:18 PM Kiley Sok via dev
wrote:
> Last remaining issue was cherry-picked. There may be one last issue with
> gRPC that's being investigated.
>
> https://github.com/apache/beam/issues/22283
>
> On Thu, Jul 2
I think there are some practical advantages to having the ability to
support a dynamic version---at previous places where I've worked having
Kafka's Schema Service was incredibly useful for data processing (it was a
Java/Scala shop and we mostly used a "decode to POJO" approach rather than
codegen.
On Fri, Aug 5, 2022 at 12:00 PM Byron Ellis wrote:
> I think there are some practical advantages to having the ability to
> support a dynamic version---at previous places where I've worked having
> Kafka's Schema Service was incredibly useful for data processing (it was a
> Java/Scala shop and we
Please review the release of the following artifacts that we vendor:
* beam-vendor-grpc-1_48_1
Hi everyone,
Please review and vote on the release candidate #1 for the version 0.1, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The c
Indeed, there's nothing stopping you from doing codegen where it's useful
but I think it's probably easier to implement codegen from dynamic than it
is to go the other way around (Avro vs Proto)
On Fri, Aug 5, 2022 at 1:15 PM Chamikara Jayalath
wrote:
>
>
> On Fri, Aug 5, 2022 at 12:00 PM Byron
+1
I verified the signatures of the artifacts, that the jar doesn't contain
classes outside of the org/apache/beam/vendor/grpc/v1p48p1 package and I
tested the artifact against our precommits using
https://github.com/apache/beam/pull/22595
On Fri, Aug 5, 2022 at 1:42 PM Luke Cwik wrote:
> Pleas
11 matches
Mail list logo
