as it does not support dynamic topics.
Thanks,
Jins George
planning to release both versions:
>
> https://issues.apache.org/jira/browse/BEAM-5419
>
> Thanks,
> Max
>
> On 31.10.18 06:28, Jins George wrote:
>> Thank you Thomas. Idea of providing different build targets for
>> runners is great, as it enables users to pick from a l
Thank you Thomas. Idea of providing different build targets for runners is
great, as it enables users to pick from a list of runner versions.
Thanks
Jins George
On 10/30/18 12:36 PM, Thomas Weise wrote:
There has not been any decision to move to 1.6.x for the next release yet.
There has
Hi Community,
Noticed that the Beam 2.8 release comes with flink 1.5.x dependency.
Are there any plans to upgrade flink to 1.6.x in next beam release. (
I am looking for the better k8s support in Flink 1.6)
Thanks,
Jins George
I am a user running beam+flink. Flink runner currently exposes only
the job level parallelism, not at an operator level. This is a really
nice feature if can be supported.
Flink's Datastream api provide that option though.
Thanks,
Jins George
On 05/16/2018 10:24 PM, Chamikara Jay
a new yarn session and submit.
Thanks,
Jins George
On 04/28/2017 09:34 AM, Frances Perry wrote:
I have the same problem and am working around it with
SerializableCoder. +1 to a real solution.
On Fri, Apr 28, 2017 at 8:46 AM, Aljoscha Krettek <mailto:aljos...@apache.org>> wrote:
Currently /org.apache.beam.runners.flink.FlinkPipelineOptions/ does not
have a way to configure externalized checkpoints. Is that something in
the road map for FlinkRunner?
Thanks,
Jins George
On 03/23/2017 10:27 AM, Aljoscha Krettek wrote:
For this you would use externalised checkpoints
configured with HDFS.
Thanks,
Jins George
On 03/22/2017 03:23 AM, Aljoscha Krettek wrote:
As I mentioned before, when running a Flink Job and simply cancelling it all
state about that job is discarded (with some exceptions, such as externalised
checkpoints). If you want the state of a Job to
state was passed to UnboundedSource.createReader() on starting
the job again.
I am currently using flink 1.1.3 and beam 0.3. I will upgrade to beam
0.6.0 and flink 1.2 and perform the tests again.
Thanks,
Jins George
On 03/21/2017 09:39 AM, Dan Halperin wrote:
hey,
The native Beam
resume from the latest offset.
If I enable Flink checkpionting with hdfs state back-end, system appears
to be resuming from the earliest offset
Is there a recommended way to resume from the offset where it was stopped ?
Thanks,
Jins George
10 matches
Mail list logo