Hello, sorry for the late reply.
EFOKinesisReader implemented the same logic of timestamps non-EFO
KinesisReader had. At the time of EFO implementation more careful
evaluation of the records' timestamps was out of context.
Can you please create an issue at https://github.com/apache/beam/issues ?
Are you talking about transform names? The main reason was because for
runners that support updating pipelines in place, the only way to do so
safely is if the runner can perfectly identify which transforms in the new
graph match the ones in the old graph. There's no good way to auto generate
names
Hmm, I'm not sure what you mean by "updating pipelines in place". Can you
elaborate?
I forgot to mention my question is posed from the context of a python SDK
user, and afaict, there doesn't seem to be an obvious way to autogenerate
names/labels. Hearing that the java SDK supports it makes me wond
Hi,
I have filed an issue: https://github.com/apache/beam/issues/28760
I have also created a PR (based of our local fix for this):
https://github.com/apache/beam/pull/28763
This can serve as a start.
Thanks
Sachin
On Mon, Oct 2, 2023 at 2:54 AM Pavel Solomin wrote:
> Hello, sorry for the late
