11/15/2016 3:44:24 PM
changes (#807)
* Combined common code in test cases (#808)
* Refined the code. Use static method.(#809)
|
11/14/2016 10:55:58 PM
activate / deactivate executor (#813)
When an executor server is launched, it uses the configured port or falls back to a default port. This behavior has been modified such that when the executor is not configured to a specific port it defaults to any available port that it can find on the machine. The advantage is that the user doesn't need to worry about port collisions when he/she doesn't need a specific port.
Also, The executor now automatically adds an entry about itself to the DB post launch. Also, it exposes the following REST APIs to allow users to activate / deactivate itself example: http://localhost:1234/executor?action=activate http://localhost:1234/executor?action=deactivate
Other changes:
* Remove public signature from interface methods
* Write port to executor.port file in working directory
* Refactored some constants which were duplicated across azkaban-common and azkaban-exec-server
|
11/11/2016 9:18:15 PM
to true. Modified local test cases to config the value and pass.
* Modified comments for execute-as-user
|
11/10/2016 12:09:37 AM
schedule page (#796)
|
11/6/2016 8:57:38 PM
3.8.0
web server (#758)
- Add method in WebUtils class to parse real client ip given HTTP headers map and client remote address - Add logic into abstract login servlet to correctly validate client IP vs IP stored for a session - Add logic in REST API to do the same - Unit tests for the above
|
11/4/2016 5:57:52 PM
uploads through Ajax interface reported HTTP code 200 when it
should be 400 or 500. There are other similar errors in this module, but this
commit only fixes failed uploads.
|
|
|
11/3/2016 3:55:00 PM
add unit test of isCronExpressionValid
* refactor code a little bit
|
10/31/2016 10:40:05 PM
3.7.0
(#786)
* Warn Users a pop up window if the cron expression string is not correct
* handle both 6 and 7 fields cases
* replace error code by Constant String
* add unit test
* update version number
|
10/27/2016 6:37:49 PM
(#769)
* Enable using log4j.properties file in conf directory (#768)
Right now, Azkaban searches for a log4j.properties file baked inside of
a jar file. This change makes the Azkaban startup script search for this
file inside of the conf directory and use it if it exists. If it does
not exist, then we will revert to using the properties file found in the
jar by default.
* Allow customization of conf directory location in startup (#768)
|
