hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-21409) Initial SessionState ClassLoader Reused For Subsequent Sessions
Date Thu, 21 Mar 2019 22:58:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-21409?focusedWorklogId=217062&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-217062
]

ASF GitHub Bot logged work on HIVE-21409:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Mar/19 22:57
            Start Date: 21/Mar/19 22:57
    Worklog Time Spent: 10m 
      Work Description: shawnweeks commented on pull request #575: HIVE-21409 Add Jars to
Session Conf ClassLoader
URL: https://github.com/apache/hive/pull/575
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 217062)
    Time Spent: 40m  (was: 0.5h)

> Initial SessionState ClassLoader Reused For Subsequent Sessions
> ---------------------------------------------------------------
>
>                 Key: HIVE-21409
>                 URL: https://issues.apache.org/jira/browse/HIVE-21409
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>            Reporter: Shawn Weeks
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: create_class.sql, run.sql, setup.sql
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> It appears that the first ClassLoader attached to a SessionState Static Instance is being
reused as the parent for all future sessions. This causes any libraries added to the class
path on the initial session to be added to future sessions. It also appears that further sessions
may be adding jars to this initial ClassLoader as well leading to the class path getting more
and more polluted. This occurring on a build including HIVE-11878. I've included some examples
that greatly exaggerate the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message