You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2015/02/24 02:22:12 UTC

[jira] [Created] (PHOENIX-1678) Detect client server jar mismatch/incomatibility by looking at the jar version stored in the MANIFEST file

Samarth Jain created PHOENIX-1678:
-------------------------------------

             Summary: Detect client server jar mismatch/incomatibility by looking at the jar version stored in the MANIFEST file
                 Key: PHOENIX-1678
                 URL: https://issues.apache.org/jira/browse/PHOENIX-1678
             Project: Phoenix
          Issue Type: Bug
            Reporter: Samarth Jain


Today, our way of detecting whether client and server jars are different is by comparing the static member variable values in MetadataProtocol.java. The check is hacky and could easily break once we start considering clusters upgraded to snapshot and "sunk" RC jars. The current mechanism is also prone to bugs when developers forget to change the member variable values even though they changed the underlying metadata. 

If the jar names could be written to a MANIFEST file, then we can have a mechanism of detecting whether client and server jars belong to different versions or if they are incompatible. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)