Posted by
rakeshchalasani on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/Cannot-determine-simple-type-name-FLINK-7490-tp20526p20567.html
Thanks for the response, the issue does look similar to FLINK-9220.
The code is part of our application, so I have to come up with an example.
But following are the steps that will likely reproduce the issue.
1. Define UDF in module, say in com.udf
2. Create a topology using the above UDF in another module, say in org.test,
and start execution in org.test.
That should reproduce the issue.
Please also note that I have only tested this using Local environment.
May be diverging from this issue, but to work around this, I refactored my
code to put the UDF in the same module but still have some reference to
another module. This didn't work locally either, but worked on the cluster.
Looking at the code, user class loader is using the path from the jar as
well, which is able to resolve package on the cluster, but locally it is not
able to get those class paths.
--
Sent from:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/