6/1/2017 3:20:21 PM
3.25.1
(#1139)
In this patch, I added two method setTriggerCondition and setExpireCondition to the Trigger Class. The reason behind is that one of our products relying on Azkaban library needs to modify Trigger object by inserting newly constructed ExpireCondition.
|
6/1/2017 2:41:52 PM
intellij plugin save actions
|
5/31/2017 9:49:30 PM
(#1136)
|
5/31/2017 6:53:19 PM
(#1133)
|
|
|
5/30/2017 2:12:18 PM
3.25.0
(#1108)
* fix AZKABAN_OPTS handling in azkaban-{web,executor}-start.sh
If the value contains spaces, the comparison causes an error
to be logged. If the reference to AZKABAN_OPTS is wrapped in
quotes, spaces are handled properly.
|
5/27/2017 12:34:19 PM
caused by UpdaterThread in ExecutorManager (#1076)"
This reverts commit de648b96e7a2479132c1b294d5784de64e668125.
* Revert running flows cache change
|
|
|
5/26/2017 4:53:02 PM
nicer debug logs because there's no stuff like "Job null finished with status SUCCEEDED".
It's also cleaner to be able to pass the ExecutableNode to the constructor instead of having to always manually call getStatus() and getNestedId().
|
5/26/2017 3:41:10 PM
used to take over 5 seconds. Now it's ~0.3 seconds.
How this was speeded up: This test was being run using the default timeout values. In the test the normal request time is so short that we can set lower timeouts in test props and still test the timeout scenarios reliably.
|
