GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/1109
[Zeppelin-1090] LivySparkSQLInterpreter doesn't work in FIFO.
### What is this PR for?
LivySparkSQLInterpreter should work in FIFO just like SparkSqlInterpreter
### What type of PR is it?
[Hot Fix]
### Todos
* [x] - LivySparkSQLInterpreter should work in FIFO just like
SparkSqlInterpreter
* [x] - add in property file zeppelin.livy.concurrentSQL
### What is the Jira issue?
* [Zeppelin-1090](https://issues.apache.org/jira/browse/ZEPPELIN-1090)
### How should this be tested?
In a notebook create 2 paragraph make content of first as
```
%livy
Thread.sleep(10000)
```
and other as
```
%livy.sql
show tables
```
The second paragraph should not get executed before first.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? n/a
* Is there breaking changes for older versions? n/a
* Does this needs documentation? n/a
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-1090
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1109.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1109
----
commit 2f1c64c859413f8a43ceeeea345a0fa195ac940d
Author: Prabhjyot Singh <prabhjyotsi...@gmail.com>
Date: 2016-06-30T10:10:25Z
add in property file zeppelin.livy.concurrentSQL
commit fe2ec72ca103b6692234604fc020701e86bc6af1
Author: Prabhjyot Singh <prabhjyotsi...@gmail.com>
Date: 2016-06-30T10:10:39Z
LivySparkSQLInterpreter should work in FIFO just like SparkSqlInterpreter
commit a2f863ee4a27b1208d4e18ca8b85b1bce6a74a38
Author: Prabhjyot Singh <prabhjyotsi...@gmail.com>
Date: 2016-06-30T10:11:01Z
check for both dead and error cases
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
