Geoffrey Jacoby created PHOENIX-3607:
----------------------------------------
Summary: Change hashCode calculation for caching
ConnectionQueryServicesImpls
Key: PHOENIX-3607
URL: https://issues.apache.org/jira/browse/PHOENIX-3607
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.8.0, 4.9.0
Reporter: Geoffrey Jacoby
Assignee: Geoffrey Jacoby
PhoenixDriver maintains a cache of ConnectionInfo ->
ConnectionQueryServicesImpl (each of which holds a single HConnection) :
The hash code of ConnectionInfo in part uses the hash code of its HBase User
object, which uses the *identity hash* of the Subject allocated at login. There
are concerns about the stability of this hashcode. When we log out and log in
after TGT refresh, will we have a new Subject?
To be defensive, we should do a hash of the string returned by user.getName()
instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
