[GitHub] zeppelin issue #2605: [ZEPPELIN-2963] Fix paragraph aborting on next run aft...
Github user namanmishra91 commented on the issue: https://github.com/apache/zeppelin/pull/2605 Agreed that should be the ideal solution but considering how tightly it is integrated with the core execution workflow, this will be a risky change and needs to be done with utmost care to avoid any side-effects. ---
[GitHub] zeppelin issue #2605: [ZEPPELIN-2963] Fix paragraph aborting on next run aft...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2605 I think the root cause is that there're 2 fields in Job.java to represent job status. (`aborted` & `status`). Why not just removing `aborted` ---
[GitHub] zeppelin issue #2605: [ZEPPELIN-2963] Fix paragraph aborting on next run aft...
Github user guptarajat commented on the issue: https://github.com/apache/zeppelin/pull/2605 This PR seems to be fixing functionality of Run All. I think if PR looks good from correctness pov then maybe we should merge this and file a follow up jira to address consistency issue, with more details about what exactly is needed. ---
[GitHub] zeppelin issue #2605: [ZEPPELIN-2963] Fix paragraph aborting on next run aft...
Github user namanmishra91 commented on the issue: https://github.com/apache/zeppelin/pull/2605 Build failures don't seem to be related to changes in this PR (selenium webdriver tests and flaky interpreter tests). Not sure what needs to be done to make them succeed. ---
