[
https://issues.apache.org/jira/browse/LIVY-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-278:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Statement cancelling improvement
> --------------------------------
>
> Key: LIVY-278
> URL: https://issues.apache.org/jira/browse/LIVY-278
> Project: Livy
> Issue Type: Improvement
> Components: REPL
> Affects Versions: 0.3
> Reporter: Saisai Shao
> Priority: Major
> Fix For: 0.10.0
>
>
> Current implementation of statement cancelling (refer from Zeppelin
> SparkInterpreter) is not so elegant and threading contention prone:
> 1. Using statement to set JobGroup is slow and ugly. Actually this could be
> done by SparkListener (tracking the mapping between statement and spark
> jobs). We should consider this with LIVY-272 to offer a sophisticated
> StatementStateListener to track the progress of statement as well as
> statement cancelling.
> 2. Current statement cancelling can only be worked with Spark jobs. If the
> statement doesn't include any spark job, the statement cannot be cancelled.
> We should think of way to handle it.
> 3. Current statement cancelling manages complex state transition and
> threading content. We should refactor to simplify or make the code easy to
> understand.
> 4. If we are still relying on setJobGroupId, move it to Interpreter interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
