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

Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2019/12/21 00:53:04 UTC

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

     [ https://issues.apache.org/jira/browse/PHOENIX-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chinmay Kulkarni closed PHOENIX-5588.
-------------------------------------

Bulk closing Jiras for the 4.15.0 release.

> 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
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-5588.master.v1.patch, PHOENIX-5588.master.v2.patch
>
>          Time Spent: 20m
>  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)