OK, thanks for the help
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
This is a safeguard in the metric system to prevent extremely long names
(as these could cause the reporting to fail); so long as the prefix is
unique you can safely ignore this warning.
On 29.11.2018 10:40, Timo Walther wrote:
Unfortunetely, renaming of operators is not supported so far.
We
Unfortunetely, renaming of operators is not supported so far.
We are currently thinking about a way of having fine-grained control
about properties of SQL operators but this is in an early design phase
and might take a while.
Regards,
Timo
Am 29.11.18 um 10:32 schrieb Kostas Kloudas:
Hi,
I
Hi,
I think that you cannot set it explicitly.
The reason that I would say that is because SQL query gets parsed through
Calcite
and then get translated to a DataStream program through a process that is
rather
opaque to the user.
That said, I also cc'ed Fabian and Timo who know more on the topic
It seems like the operator name for a SQL group by is the query string
itself. I get
"The operator name groupBy: (myGroupField), select: (myGroupField,
someOther... )... exceeded the 80 characters length limit and was truncated"
Is there a way to name the SQL query operator?
--
Sent from: http
