Reload of aux jars on HiveServer2 failing

[Shashank Pedamallu <sh...@gmail.com>]

Hi,

I have a jar that is configured under hive.reloadable.aux.jars.path. Upon
updating the jar and successful execution of *RELOAD;* command via Beeline,
the latest jar is not getting picked up. These are the steps I followed:
0. Started hs2 process with --hiveconf hive.reloadable.aux.jars.path=
<desired_jar_absolute_path>
1. Removed the *desired_jar*
2. Added an updated jar (that has some log statements) with same name in
the same location as *desired_jar_absolute_path*
3. Connected to HS2 process via Beeline and issued a RELOAD; command
4. Ran a query that should have emitted a log statement as per updated jar.
But it was not.

Please note that if I did a restart of hs2 process, the latest jar is being
picked and the log statements are getting printed.

Could someone please help me if I'm not using the RELOAD command right or
if there is a known issue surrounding it.

Thanks in advance!
-Shashank

Re: Reload of aux jars on HiveServer2 failing

[Adam Szita <sz...@cloudera.com>]

Hi Shashank,

First of all make sure your jar is not on a path configured for the
non-reloadable jars as well i.e. hive.aux.jars.path; it should only be on
the reloadable one.

As far as I know RELOAD statement creates new classloader over the old one
to make sure new jar content is loaded, however, you could try the
following:
After removing the old jar from your path execute a RELOAD. Then put your
new jar on the path and hit RELOAD again, and run your query.

Hope that helps.

Adam

On 8 March 2018 at 00:37, Shashank Pedamallu <sh...@gmail.com>
wrote:

> Hi,
>
> I have a jar that is configured under hive.reloadable.aux.jars.path. Upon
> updating the jar and successful execution of *RELOAD;* command via Beeline,
> the latest jar is not getting picked up. These are the steps I followed:
> 0. Started hs2 process with --hiveconf hive.reloadable.aux.jars.path=
> <desired_jar_absolute_path>
> 1. Removed the *desired_jar*
> 2. Added an updated jar (that has some log statements) with same name in
> the same location as *desired_jar_absolute_path*
> 3. Connected to HS2 process via Beeline and issued a RELOAD; command
> 4. Ran a query that should have emitted a log statement as per updated jar.
> But it was not.
>
> Please note that if I did a restart of hs2 process, the latest jar is being
> picked and the log statements are getting printed.
>
> Could someone please help me if I'm not using the RELOAD command right or
> if there is a known issue surrounding it.
>
> Thanks in advance!
> -Shashank
>