8/31/2018 5:56:04 PM
3.55.0
intention of the original test is to verify if the condition is null, it should take the default value all_success. Modify the test case to make it clear and stable.
|
8/31/2018 5:55:47 PM
release in CI environment.
|
8/30/2018 7:43:58 PM
3.54.0
jobtype for reportal. User is able to run presto query through reportal UI with a shared presto account defined in jobtype plugin config. Presto account password could be encrypted and kept in the config file, and it requires a key path file which could be defined in jobtype plugin config to decrypt.
|
8/30/2018 4:02:31 PM
deploy latest master to our staging cluster. The observation of this bug is all execution history table is missing.

The cause looks like a javascript or backbone grammar issue.
The fix is quite simple.
|
8/27/2018 2:23:16 PM
3.52.03.53.0
workflow - validate conditions
* Address comments
|
8/23/2018 9:01:23 PM
(#1927)
* Conditinal workflow - modify conditionOnJobStatus macros.
* fix flaky test
* fix flaky test2
|
8/23/2018 8:59:54 PM
jobtype for reportal.
Tableau is not real-time: whenever users want to incorporate the newest data into their visualization, they must refresh the extracted data. This tells Tableau to get and show whatever new data has come into the data sources. It's natural for users to want to automatically trigger Tableau refreshes when their jobs are done and their data sources are full of new data. This job is designed to do exactly that - refreshing a Tableau workbook whenever run so users don't have to do so manually.
Since tableau workbook refresh doesn't require authentication, all users have to do is identify the name of the workbook they'd like to refresh and it will do so.
|
8/23/2018 5:15:19 PM
(#1923)
* Fix flaky test and remove sleep time in FlowRunnerYamlTest.
* fix flaky test
|
8/23/2018 2:08:03 PM
issue #1796. A new property called azkaban.display.numOfExecutions will be added in the azkaban.properties and be used to determine the number of rows to be displayed.
As it will default to 16 when the property does not exist, it will not have any impact on the existing page size.
|
8/22/2018 2:28:51 PM
3.51.4
(#1933)
Flow trigger classes will be serialized and persisted in quartz tables and deserialized back.
If serialVersionUID is not defined specifically, JVM would generate a default id in runtime which is dependent on compiler implementation, and and can thus result in unexpected nvalidClassExceptions during deserialization if new deployment has different serialVersionUID from old deployment which has been persisted in db.
Why choose those numbers(-1330280892166841227L ...)?
To be backward compatible since those are the serialVersionUID of first deployment of flow trigger classes and already have been persisted in database.
|
