I think I've narrowed it down to this function in ExtractionUtils
public static Optional> extractSimpleGeneric(
Class baseClass, Class clazz, int pos) {
try {
if (clazz.getSuperclass() != baseClass) {
return Optional.empty();
}
Application mode. I've done a bit more research and created
https://issues.apache.org/jira/browse/FLINK-29288, planning to work on a PR
today.
TLDR: currently Flink operator always creates /opt/flink/usrlib folder and
forces you to specify the jarURI parameter, which is passed as
pipeline.jars / p
Thank you for the clarification. I thought so to,
Unfortunately my state are generics based and those are definitely not
treated as a POJO , though it has all the constructs ( no arg constructor,
getters/setters etc ). I will likely take an at least once hit by
Changing the uid of that specific O
Hi Hailu,
If you take a look at the history of ExecutionMode [1], apart from the
refactoring commit, this class is introduced before the year 2016, in which
DataSet API has not been deprecated.
>From my point of view, you should set runtime mode [2] instead of execution
>mode currently if usin
Are you deploying the job in session or application mode? Could you provide
the stacktrace. I'm wondering whether that would be helpful to pin a code
location for further investigation.
So far, I couldn't come up with a definite answer about placing the jar in
the lib directory. Initially, I would
