You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce alternative "rich" UDFs to operators. These functions will have access to (at least) the following:
publicinterfaceRichUnaryFunction<IN, OUT> extendsUnaryFunction<IN, OUT> {
/** Called before the first element. */voidinit(Contextcontext);
/** The UDF itself. */@OverrideOUTapply(INelem);
/** Called after last element (might not necessarily be absolutely last element, but at least another `init` will be called before next `apply` */voidclose();
}
The Context passed into init should be the same as the one passed to Functor versions. We must make sure that the current code doesn't break (mostly in terms of using lambdas where appropriate), that is, we either create separate calls with these rich function variants, or we will add these calls to "standard" UDFs, but with default empty implementation.
The text was updated successfully, but these errors were encountered:
Introduce alternative "rich" UDFs to operators. These functions will have access to (at least) the following:
The
Context
passed intoinit
should be the same as the one passed toFunctor
versions. We must make sure that the current code doesn't break (mostly in terms of using lambdas where appropriate), that is, we either create separate calls with these rich function variants, or we will add these calls to "standard" UDFs, but with default empty implementation.The text was updated successfully, but these errors were encountered: