Hi Rong,
Yes, what Jark described is exactly whet I need. Currently we have a work
around for this problem, by using a UDF whose result type is a Map. I will took
a look on your proposals and PR.
Thanks for your help and suggestions.
Best,
Wangsan
> On Dec 1, 2018, at 7:30 AM, Rong Rong
Hi Wangsan,
If your require is essentially wha Jark describe, we already have a
proposal following up [FLINK-9249] in its related/parent task:
[FLINK-9484]. We are already implementing some of these internally and have
one PR ready for review for FLINK-9294.
Please kindly take a look and see if
Hi Wangsan,
If I understand correctly, you want the return type of UDTF is determined
by the actual arguments, not a fixed result type. For example:
udtf("int, string, long", inputField)returns a composite type with
[f0: INT, f1: VARCHAR, f2: BIGINT]
udtf("int", inputField)returns an
Hi Wangsan,
currently, UDFs have very strict result type assumptions. This is
necessary to determine the serializers for the cluster. There were
multiple requests for more flexible handling of types in UDFs.
Please have a look at:
- [FLINK-7358] Add implicitly converts support for
Hi all,
When using user-defined table function in Flink SQL, it seems that the result
type of a table function must be determinstic.
If I want a UDTF whose result type is determined by its input parameters, what
should I do?
What I want to do is like this:
```
SELECT input, f1, f2 length
