9/24/2018 3:58:10 PM
3.59.0
(#1963)
This reverts commit b70ee97.
Reportal has to work with internal version of presto JDBC instead of OSS version.
|
9/19/2018 10:17:33 PM
3.58.0
jdbc is required by presto reportal jobtype.
|
9/19/2018 9:46:24 PM
summary (#1958)
* Conditional workflow UI support - add condition in job info and flow summary.
* address comment
|
|
|
|
|
|
|
9/14/2018 6:58:49 PM
is synchronized, one thread might block all others from entering into this method when it's stuck fetching token. So it's important to prompt users about which step the job is stuck with.
|
9/14/2018 3:26:33 PM
Fix flaky test of runFlowOnJobStatusConditionNull
* Fix flaky test runFlowOnJobStatusConditionNull_2
|
9/13/2018 8:23:24 PM
by using a non-zero wait time when the while loop won't be exited immediately after first wait.
- Reorganize code to improve readability
|
9/13/2018 5:58:12 PM
had a recursion loop like this:
selectExecutorAndDispatchFlow -> handleDispatchExceptionCase -> selectExecutorAndDispatchFlow -> ..
..with max depth of activeExecutors.size()
Iterative approach is easier to reason about, and is totally safe against StackOverflowError.
This is also preliminary refactoring to eventually allow configuring higher max for dispatching errors. Currently, however, max dispatch attempts is capped by the total number of active executors (because each executor is only tried once). In the future I'd like to remove that limit and rely solely on the MAX_DISPATCHING_ERRORS_PERMITTED property.
|
