Github user HeartSaVioR commented on the issue:
https://github.com/apache/flink/pull/6252
@fhueske
Ah I didn't notice the object is already existing. Thanks for letting me
know!
---
Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/6252
I think it can also be a new public method in
`org.apache.flink.table.expressions.ExpressionUtils`.
Thanks, Fabian
---
Github user HeartSaVioR commented on the issue:
https://github.com/apache/flink/pull/6252
@fhueske
Yeah, that would be great. I'm happy to revert the change and introduce new
class.
I'm just not sure where to place and how to name it, since it will be going
to have
Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/6252
Thanks for opening this PR @HeartSaVioR! (cc @twalthr)
I thought about this again and I don't think we should make the method
public. The problem is that `Expression` is one of the core
