[jira] [Created] (TEPHRA-194) Transaction client should not retry startShort() if an invalid timeout is given

Andreas Neumann created TEPHRA-194: -- Summary: Transaction client should not retry startShort() if an invalid timeout is given Key: TEPHRA-194 URL: https://issues.apache.org/jira/browse/TEPHRA-194 Pr

[jira] [Updated] (TEPHRA-194) Transaction client should not retry startShort() if an invalid timeout is given

[ https://issues.apache.org/jira/browse/TEPHRA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-194: --- Description: Currently, if an invalid timeout (negative, or too long) is given, the Tx manage

[jira] [Commented] (TEPHRA-194) Transaction client should not retry startShort() if an invalid timeout is given

[ https://issues.apache.org/jira/browse/TEPHRA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583785#comment-15583785 ] Andreas Neumann commented on TEPHRA-194: Question: ideally we will introduce a new

What's our policy for Thrift changes?

Hi all, As part of https://issues.apache.org/jira/browse/TEPHRA-194, it would make sense to introduce a new exception type in the thrift module. That may break wire compatibility with previous versions. I am wondering what the current policy is for changing the Thrift protocol?Can we safely assum

Re: What's our policy for Thrift changes?

Hi Andreas, Phoenix can't assume that the client and server are the same version as we support rolling upgrades for patch and minor upgrades. It'd only be ok for a major release. Thanks, James On Monday, October 17, 2016, Andreas Neumann wrote: > Hi all, > > As part of https://issues.apache.org/