Hi Yufan,
In general, I think it's okay to remove these features.
But could you elaborate If there will be missing functionality after we remove
these two subscriptions support?
On 2022/12/14 13:01:53 盛宇帆 wrote:
> Hi Zili,
>
> Thanks for picking up this discussion. Here is my answer:
>
> I
Hi there,
We have a pyflink/SQL job that has a bug that we fixed and are trying to
deploy. Here's the issue though. The job successfully restores from the
checkpoint, but has no recent savepoints. We can't seem to get it to accept
our new SQL unless we savepoint/restore, but we can't trigger a
Hi Ken,Without knowning the details, the first thing I would suggest to check is whether you have reached a threshold which is configured in your state storage (e.g., s3) therefore your further download were throttled. Checking your storage metrics or logs should help to confirm whether this is
Hi Yufan,
I'm also looping in the Dev mailing list for awareness.
>From my perspective, it sounds like it makes more sense to drop the Shared
and Key_Shared subscription. If it's currently unstable/not usable and
there are alternatives that you can leverage with Flink (like the increased
Hi,
We recently switched to the flink-s3-fs-presto library for checkpointing in
Flink 1.16.0 and we would like to get client-side metrics from the Presto
S3 client (request rate, throttling rate, etc).
I can see that the upstream client from Presto 0.272 already comes with a
metric collector
Hello all!
We are trying to bring our flink job closer to real-time processing and
currently our main issue is latency that happens during checkpoints. Our
job uses RocksDB with periodic checkpoints, which are a few hundred GBs
every 15 minutes. We are trying to reduce the checkpointing duration
Hi Martijn,
thanks for referencing both related FLIPs and providing a recommendation. That
was already helpful. I need to find some time to further investigate this
topic. So far I agree that it might be the most reasonable approach to just use
the Kafka timestamp to carry the event time.
Same error again today. Any tips ? I'm considering downgrading to Flink
1.14 ?
On Wed, Dec 14, 2022 at 11:51 AM Lars Skjærven wrote:
> As far as I understand we are not specifying anything on restore mode. so
> I guess default (NO_CLAIM) is what we're using.
>
> We're using ververica platform
Hi Lincoln,
Thanks very much for the reply! The issue seems to occur both in local
development in the IDE, and when running in a Flink cluster. Below is the full
Java code to replicate the issue. I generated an empty project following the
instructions at
