Please unsubscribe me
ere not able ?
> Because this really seems to be a case for moving to event time timers. I
> think that would require some effort (including choosing a good watermark
> strategy) but then would solve all your problems.
>
> Frank
> On 08.02.22 08:42, Alex Drobinsky wrote:
>
>
ave ever met
> when restoring the timers?
>
> Flink does not support to remove state (including timer state) currently.
>
> Best
> Yun Tang
> ------
> *From:* Alex Drobinsky
> *Sent:* Monday, February 7, 2022 21:09
> *To:* Caizhi Weng
> *Cc
tch aggregation [1] solve your problem?
>
> [1]
> https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/dev/table/tuning/#minibatch-aggregation
>
> Alex Drobinsky 于2022年2月3日周四 20:41写道：
>
>> Dear flink user,
>>
>> In our project, restoring the timer'
Dear flink user,
In our project, restoring the timer's state creates numerous issues, so I
would like to know
if it is possible to avoid save/restore of timers altogether.
If it isn't possible, how could I delete all registered timers during the
open function ?
Best regards,
Alexander
e it (or just go with a lazy access
> pattern all the way).
>
> On Tue, Oct 12, 2021 at 2:55 PM Alex Drobinsky
> wrote:
>
>> Hi Jing,
>>
>> Job doesn't restart from the checkpoint, it's a brand new clean job , no
>> exceptions happened during executio
eBackend to see
>>whether the transient field could be read as expected, the answer should
>> be
>>yes.
>>2. After restoring from checkpoint, check whether could read the
>>transient field back if using FileSystemStateBackend.
>>
>>
>
в 16:50, JING ZHANG :
> Hi Alex,
> It is a little weird.
> Would you please provide the program which could reproduce the problem,
> including DataStream job code and related classes code. I need some debug
> to find out the reason.
>
> Best,
> JING ZHANG
>
>
> A
choose RocksDBStateBackend, I thought it was expected behavior
> because RocksDBStateBackend stores all state as byte arrays in embedded
> RocksDB instances. Therefore, it de/serializes the state of a key for every
> read/write access. CurrentFile is null because the transient variable
> woul
Dear flink community,
I have following state class ( irrelevant fields removed )
public class MultiStorePacketState implements Serializable {
public transient RandomAccessFile currentFile = null;
public long timerValue;
public String fileName;
public String exportedFileName;
p
sider the possibility
> of users mounting the configuration directly, and instead assumed that
> modifications to the config always go through the FLINK_PROPERTIES
> environment variable.
>
> That would also be the workaround for your issue.
>
> On 5/12/2021 2:06 PM, Alex Drobins
Dear flink community,
First I need provide some minimum information about my deployment scenario:
I'm running application inside of Flink docker, below original Dockerfile:
---
FROM flink:1.13.
Dear entity that represents Flink user community,
In order to formulate the question itself, I would need to describe the
problem in many details, hence please bear with me for a while.
I have following execution graph:
KafkaSource -> Message parser -> keyBy -> TCP assembly -> keyBy -> Storage
-
13 matches
Mail list logo
