You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2019/12/04 15:08:00 UTC

[jira] [Commented] (PHOENIX-5588) Client-Server Incompatibility False Alarm

    [ https://issues.apache.org/jira/browse/PHOENIX-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987934#comment-16987934 ] 

Istvan Toth commented on PHOENIX-5588:
--------------------------------------

It turns out the chance of throwing a misleading exception is not small at all, even with my first patch.

Rather than trying to enumerate and white/blacklist the failure cases, use the standard HBase exception parser, and let the user interpret the cause.

> Client-Server Incompatibility False Alarm
> -----------------------------------------
>
>                 Key: PHOENIX-5588
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5588
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.3
>            Reporter: Geoffrey Jacoby
>            Assignee: Istvan Toth
>            Priority: Minor
>              Labels: beginner, newbie
>         Attachments: PHOENIX-5588.master.v1.patch, PHOENIX-5588.master.v2.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In ConnectionQueryServicesImpl.checkClientServerCompatibility, the method assumes that any exception that's not a SQLException is because the client and server jars are incompatible. However, an HBase level exception (such as NotServingRegionException or TableNotFoundException) can occur even if the jars are compatible. 
> This results in a confusing, incorrect message in the logs that can send operators in the wrong direction. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)