Hi, Yifan.
Unfortunately, IIUC, we could get the key and value type only by reading
related sql codes currently.
I think it's useful if we could support SQL semantics for the Processor
API, but it indeed will take lots of effort.
On Thu, Sep 21, 2023 at 12:05 PM Yifan He via user
wrote:
> Hi
Hi Hangxiang,
I still have one question about this problem, when using datastream api I
know the key and value type I use in state because I
defined ValueStateDescriptor, but how can I get the ValueStateDescriptor in
flinksql?
Thanks,
Yifan
On 2023/09/07 06:16:41 Hangxiang Yu wrote:
> Hi,
Hi Hangxiang,
We are using flink 1.14, the state backend is EmbeddedRocksDBStateBackend ,
and the Checkpoint Storage is filesystem.
This is the checkpoint configuration from our running jobs
Checkpointing Mode Exactly Once
Checkpoint Storage FileSystemCheckpointStorage
State Backend
Hi, Yifan.
Which flink version are you using ?
You are using filesystem instead of rocksdb so that your checkpoint size
may not be incremental IIUC.
On Thu, Sep 7, 2023 at 10:52 AM Yifan He via user
wrote:
> Hi Shammon,
>
> We are using RocksDB,and the configuration is below:
>
Hi, Yifan.
If you enable the debug level log, you could see the log like 'Generated
hash xxx for node xxx'. I haven't found other ways to find the operator id
of SQL jobs, maybe I missed something, or we should export this info more
directly.
Unfortunately, there is no default state name for an
Hi Hangxiang,
Thanks for your answer! We are using RocksDB state backend, and the
incremental checkpoint is enabled, and it is the incremental size keeps
increasing. We didn't add any custom checkpoint configuration in flink sql
jobs, where can I see the log of
Hi Shammon,
We are using RocksDB,and the configuration is below:
execution.checkpointing.externalized-checkpoint-retention:
RETAIN_ON_CANCELLATION
execution.checkpointing.max-concurrent-checkpoints: 1
execution.checkpointing.min-pause: 0
execution.checkpointing.mode: EXACTLY_ONCE
