Impala retries even when "SetError(const char* error_msg)" Error is set in UDF.

RPAT — Fri, 16 Sep 2022 12:11:20 GMT

Hi All,

In UDF executing the context->SetError(const char* error_msg) method impala again retries the UDF.

Below is my UDF:-

IntVal my_udf(
FunctionContext* context,
IntVal& sInput
)
{
if( sInput.val == 0 )
{
context->SetError( "Off Value" );
return 0;
}
IntVal iResult(sInput.val + 1);
return iResult;
}

DDL :--

CREATE FUNCTION my_udf(INTEGER) RETURNS INTEGER
LOCATION '/opt/impala/udfs/myudf.so'
SYMBOL = 'my_udf';

So if we debug this UDF using GDB.

If we add the break point at "context->SetError( "Off Value" );" this line then we come to know that if we pass 0 to this UDF this will hit the break point more than one time.

So please let me know that it is right behavior?

i ran this UDF in CDH 5.10 & CDH 5.11.

Re: Impala retries even when "SetError(const char* error_msg)" Error is set in UDF.

Tim Armstrong — Sat, 30 Sep 2017 00:21:24 GMT

I just saw this in my email backlog. Yes this is the expected behaviour. Your UDF may be called again on the same thread or a different thread. After you call SetError() the query will fail but the error will take some time to propagate.

question Re: Impala retries even when "SetError(const char* error_msg)" Error is set in UDF. in Archives of Support Questions (Read Only)

Impala retries even when "SetError(const char* error_msg)" Error is set in UDF.

Re: Impala retries even when "SetError(const char* error_msg)" Error is set in UDF.