Deprecate execution.isolation.thread.timeoutInMIlliseconds property name in favor of execution.timeoutInMilliseconds

[mattrjacobs]

Given change in #664, make sure that both styles of naming the timeout property work, and setting both chooses the new-style

[mattrjacobs]

I still want to do this feature, but the revert in #675 makes it not critical for 1.4.0. Will push to 1.4.x

[dmak]

closed = the new property will not get into master? Or is it already in 2.0.x branch?

[mattrjacobs]

Both properties are in master. 2.x branch is not active at this point

[dmak]

@mattrjacobs As far as I can see the original commit 60e47c1 was reverted by a2c5112 on 15 Feb 2015. The code in master reads the property execution.isolation.thread.timeoutInMilliseconds, see HystrixCommandProperties:123. Please forgive me if I have missed something... maybe you could point me the line where execution.timeoutInMilliseconds property is read? Thanks!

[mattrjacobs]

@dmak Apologies - you are correct. The property is only configurable via the key execution.isolation.thread.timeoutInMilliseconds in master.

[dmak]

Then the questions is still opened: in what Hystrix version will this fix be available?

[mattrjacobs]

As of right now, no one is working on it.

[dmak]

Then this ticket should be re-opened, because the support of execution.timeoutInMilliseconds property is not applied.