[
https://issues.apache.org/jira/browse/LIVY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
weiwenda updated LIVY-544:
--------------------------
Description:
* 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}
was:
* when user's main usage scenario is not sensitive to the order of execution,
sush 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 sush requirement.
bq. private val interpreterExecutor =
ExecutionContext.fromExecutorService(Executors.newSingleThreadExecutor())
> 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)
