[
https://issues.apache.org/jira/browse/LIVY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781202#comment-16781202
]
weiwenda edited comment on LIVY-544 at 3/1/19 2:03 AM:
-------------------------------------------------------
As you've said, it's important to keep the abililty to choose scheduler pool
on a per-statement level. But to simplify the configuration of
livy-fairscheduler.xml, i just create a new statement type "serial_sql" to
provide such ability.
If user query a creating table, both ddl sql and dml sql should submit as
serial_sql type. Maybe this is not a elegant solution, but will not modify the
json format of statement as least.
was (Author: [email protected]):
As you've said, it's important to keep the abililty to choose scheduler pool
on a on a per-statement level. But to simplify the configuration of
livy-fairscheduler.xml, i just create a new statement type "serial_sql" to
provide such ability.
If user query a creating table, both ddl sql and dml sql should submit as
serial_sql type. Maybe this is not a elegant solution, but will not modify the
json format of statement as least.
> 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)
