Hi Yuval,
Thanks for pointing that out. Yes, metrics names would also be affected.
The need sounds reasonable, we could create a JIRA and give a detailed
description of the requirements.
cc @godfrey @Kurt to provide more user perspective, they may be interested
in the feature.
Best,
JING ZHANG
Hi Jing,
An additional challenge with the current Table API / SQL approach for
iperator naming is that it makes it very hard to export metrics, i.e. to
track watermarks with Prometheus, when operator names are not assignable by
the user.
On Wed, Jul 28, 2021, 13:11 JING ZHANG wrote:
> Hi
Hi Clemens,
This feature is temporarily not supported.
Your needs sounds reasonable, you could create a JIRA ticket.
Now operator name contains a lot of detailed information, it has advantages
and disadvantages.
When we need troubleshoot problems, detailed information could help us to
know what
Is it possible to rename execution stages from the Table API? Right now the
entire select transformation appears in plaintext in the task name so the
log entries from ExecutionGraph are over 10,000 characters long and the log
files are incredibly difficult to read.
for example a simple selected
