Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3607

Change hashCode calculation for caching ConnectionQueryServicesImpls

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • 4.8.0, 4.9.0
    • None
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            gjacoby Geoffrey Jacoby
            gjacoby Geoffrey Jacoby
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: