[
https://issues.apache.org/jira/browse/PHOENIX-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor resolved PHOENIX-1483.
-----------------------------------
Resolution: Fixed
Fix Version/s: 4.3
> Support mixed client versions against newer server version
> ----------------------------------------------------------
>
> Key: PHOENIX-1483
> URL: https://issues.apache.org/jira/browse/PHOENIX-1483
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Fix For: 4.3
>
>
> Our backward compatibility story between client and server to date has been:
> 1) update the server Phoenix jar first with the new release. Clients one
> minor release back will continue to work with the new server jar (this is the
> scenario for which we test).
> 2) upgrade *all* client versions to the new Phoenix jar
> If there's any upgrade code that needs to run, it will run at step (2), when
> the first time a new client connects to the cluster. It's possible that the
> upgrade code would make a change such that the older clients would no longer
> work. An example is between 4.1 and 4.2 in which the sequence table was
> salted to improve performance. Once it's salted (i.e. first time any 4.2
> client connects with the 4.2 server), then sequences in 4.1 clients will no
> longer work. FWIW, you can set the client-side phoenix.sequence.saltBuckets
> to 0 in your hbase-sites.xml and this particular upgrade will not take place
> (nor will you get the performance gain, of course).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
