taking in parameters based on the table's column
values (then no constant propagation).
From: PradeepKumar Yadav
Sent: Sunday, May 13, 2018 11:44 PM
To: Jason Dere; user@hive.apache.org
Subject: RE: Hive Custom UDF evaluate behavior when @UDF
Jason Dere [mailto:jd...@hortonworks.com]
Sent: Monday, April 16, 2018 11:18 PM
To: PradeepKumar Yadav
mailto:pradeep.ya...@protegrity.com>>;
user@hive.apache.org<mailto:user@hive.apache.org>
Subject: Re: Hive Custom UDF evaluate behavior when @UDFType is set
I'd suggested log
xception("initialize");
From: PradeepKumar Yadav
Sent: Monday, April 16, 2018 4:53 AM
To: user@hive.apache.org
Cc: Jason Dere
Subject: FW: Hive Custom UDF evaluate behavior when @UDFType is set
Hi,
Regarding the previous mail sent, I have attached following
: Monday, April 9, 2018 11:35 PM
To: user@hive.apache.org
Subject: Hive Custom UDF evaluate behavior when @UDFType is set
Hi,
Recently while creating a custom generic hive UDF I came across
a different behavior for the Evaluate method. The custom UDF had a logic to
increment the
Hi,
Recently while creating a custom generic hive UDF I came across
a different behavior for the Evaluate method. The custom UDF had a logic to
increment the counter and write it to a file. Now when I execute it directly
without involving any table it always returns an extra coun
