stoty commented on PR #2027: URL: https://github.com/apache/phoenix/pull/2027#issuecomment-2485171795
> > Even if the UGI call is shortcut and quick when we are already logged in as the requested principal (did not check), the original HBaseConfiguration performance regression remains in this case. > > Yes, but this is still fine for the given Jira right? In a follow-up Jira, we can fix new config + UGI setup if possible? My quoted reply was wrong, I have edited it out in the meantime, @lokiore was right. Yes, we can use the current patch as is, or implement my suggested change to make sure that we never need to create a full HBaseConfiguration object. -- 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. To unsubscribe, e-mail: issues-unsubscr...@phoenix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
