[
https://issues.apache.org/jira/browse/PHOENIX-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991816#comment-16991816
]
Hudson commented on PHOENIX-5588:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.5 #211 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.5/211/])
PHOENIX-5588 Client-Server Incompatibility False Alarm (stoty: rev
7a4c7ab3cb20090bf868fa96e7aa54c923bd5bdb)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
> 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: 5.1.0, 4.15.1
>
> 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)
