You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2019/11/25 18:02: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=16981756#comment-16981756 ] 

Geoffrey Jacoby commented on PHOENIX-5588:
------------------------------------------

[~neha.gupta] [~fengchristine] [~stoty] [~yanxinyi] - this is a good beginner JIRA if any of you have the time and interest. 

> 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
>            Priority: Minor
>              Labels: beginner, newbie
>
> 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)