[
https://issues.apache.org/jira/browse/LIVY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789739#comment-16789739
]
Ruslan Dautkhanov commented on LIVY-544:
----------------------------------------
Thanks for explaining.
This is a great improvement . I know some our users do use concurrent SQL in
Zeppelin.
To make this not a breaking change, can we treat current `codeType`==`SQL` as a
serial execution SQL (current Livy behavior).
And instead of introducing `SerialSQL` like you did in the PR, let's introduce
`concurrentSQL` like in Zeppelin.
This would be non-default, new behavior you're proposing.
I see this change would be less disruptive for current Livy users.
Thank you.
> Statements in a Session must execute one by one which is time-consuming
> -----------------------------------------------------------------------
>
> Key: LIVY-544
> URL: https://issues.apache.org/jira/browse/LIVY-544
> Project: Livy
> Issue Type: Improvement
> Components: REPL
> Affects Versions: 0.5.0
> Reporter: weiwenda
> Priority: Minor
> Labels: performance
>
> * when user's main usage scenario is not sensitive to the order of execution,
> such as sql Session Kind, user may hope livy server can deal with multi
> statement concurrentlly
> * but as interpreterExecutor initialized as singleThreadExecutor, it's no
> possible to satisfy such requirement.
> {quote}private val interpreterExecutor =
> ExecutionContext.fromExecutorService(Executors.newSingleThreadExecutor())
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
