Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/191
> Would an alternative be to not rely on the User.equals method, but
instead modify ConnectionInfo.equals to do some other kind of equality check on
User?
I think I initially had this idea too (wondering why User doesn't implement
a "normal" value-based equals/hashCode implementation). Devaraj didn't remember
exactly why, but he recalled that there was a reason that UGI (and thus User
also) did this. I could try to dig into the Hadoop archives to see if I can
understand why this was done.
Mostly, I think this approach keeps us in line with what HDFS and HBase
does now which has some value.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
