[
https://issues.apache.org/jira/browse/PHOENIX-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-100:
---------------------------------
Attachment: patch.diff
> Relax compatibility check to only check that the major version matches
> between the client and server jars
> ---------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-100
> URL: https://issues.apache.org/jira/browse/PHOENIX-100
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 3.0.0
>
> Attachments: patch.diff
>
>
> Phoenix uses a standard dot-separated, three number versioning scheme: <major
> version>.<minor version>.<patch version>. For example, for 1.2.3, the major
> version would be 1, the minor version 2, and the patch version 3.
> In earlier versions of Phoenix, only the patch version was allowed not be
> different between the client and server, not the major and minor versions. If
> they didn't match, an "Incompatible jar" exception is thrown at startup time.
> As of 3.0, Phoenix allows both the patch and minor version to different -
> only the major version must be the same between the client and server. The
> minor version is typically changed if a new expression type is introduced,
> such as a new built-in function. With the new scheme, care must be taken to
> first deploy a new jar to the server. This will prevent the client from
> attempting to use functionality that is not yet available on the server.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
