[PHOENIX-6129] Optimize tableExists() call while retrieving correct MUTEX table

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.0, 4.15.0
• Fix Version/s: 5.1.0, 4.16.0
• Labels: phoenix-hardening quality-improvement
• Assignee: Viraj Jasani
• Reporter: Chinmay Kulkarni
• Created: 12/Sep/20 00:44
• Updated: 26/Oct/20 22:47
• Resolved: 26/Oct/20 20:33

Description

Inside CQSI.writeMutexCell(), we call getSysMutexPhysicalTableNameBytes() which in turn calls HBase Admin APIs to check the existence of SYSTEM.MUTEX/SYSTEM:MUTEX here.

Later, we anyways try to get the HTable both inside writeMutexCell() and deleteMutexCell(). Instead, we can lazily fail this getTable() call (by catching the HBase TableNotFoundException) to avoid additional HBase Admin API calls.

Issue Links

• links to: GitHub Pull Request #920