Hi Megh,
Unfortunately, Flink currently does not expose operator IDs via REST API, nor
log them unless some operators' states are missing during state recovery as
operator IDs are mostly used internally. Could you further collaborate a bit on
why you need the operator ID info? Maybe you can
Hi,
请发送任意内容的邮件到 user-zh-unsubscr...@flink.apache.org 来取消订阅邮件。
Best,
Yunfeng
On Wed, Oct 4, 2023 at 10:07 AM 1 wrote:
>
>
Hi team,
I am looking to understand parity in Table API and SQL API.
Would you say that we have parity for UDF?
I see the TableAggregateFunction can not be represented in Flink SQL but
only in Table API. Have you known it to work like other UDFs?
So, I was able to get the rollback to work after I changed my upgradeMode
to *last-state*. Previously, my upgradeMode was *savepoint*, and when I
deployed a bad commit, the jobmanager-leader configmap would get deleted.
Once I changed the upgradeMode to *last-state*, the configmap was retained
I am trying to understand the Flink design pattern for consuming files from
S3 continuously as they appear. I have written the below minimal program to
do that and it works as expected wrt detecting newly-uploaded S3 files
within the configured 5 second monitoring poll period. Then it just prints
Hi,
Is it possible to delay a window trigger without changing window-end and
window-start times?
Thanks
Hello community,
We're making use of uid method on all the stateful operators to assign
custom operator id's.
However, I don't see any reference to these operator id's anywhere in the
job logs or Flink UI or even checkpoint details.
Do I need to look into some other place?
Thanks,
Megh
Yes, that also works correctly, at least based on the Kafka source we use
(we'd get an alert if it suddenly started consuming from a very old offset).
Regards,
Alexis.
On Thu, 5 Oct 2023, 19:36 ramkrishna vasudevan,
wrote:
> Sorry for the late reply. Just in case you restart the job , is it
