GitHub user qwemicheal opened a pull request:
https://github.com/apache/zeppelin/pull/2390
[ZEPPELIN-2589]Let zeppelin show more than one line of error log returned
by livy.
### What is this PR for?
Let zeppelin show more than one line of error log returned by livy.
### What type of PR is it?
Improvement
### What is the Jira issue?
[ZEPPELIN-2589
](https://issues.apache.org/jira/browse/ZEPPELIN-2589)
### How should this be tested?
1. build: mvn clean package -DskipTests;
2. /bin/zeppelin-daemon.sh restart
3. Start a notebook
4. Use Livy interpreter and input some erroneous spark code, check the
shown result is more than one line
### Screenshots (if appropriate)
before
after
### Questions:
* Does the licenses files need update?No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/qwemicheal/zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2390.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 #2390
----
commit 905c54d7607fd07d25c3369fb1f7cf200c3a2460
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-05-27T07:21:32Z
add traceback msg from livy return json to InterpreterResult
commit 2eb6011509b7c4b4ba76b066a9f862143b515e48
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-05-27T07:33:59Z
add traceback msg from livy return json to InterpreterResult
commit f6135ccee2dde09ac088fc7f9c20fad7f881b47a
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-05-27T07:44:33Z
add traceback msg from livy return json to InterpreterResult
commit 45c5d9f0a3b99b6f4302ed845607e6eca939fdd4
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-05-27T07:47:52Z
add traceback msg from livy return json to InterpreterResult
commit 5a03e05f557bb54ef013cefb8ceb9d7c345e7a7a
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-05-27T10:40:18Z
add check for livy 0.2 when traceback field is missing
commit 04061d3b3cf3ed6e8ee7af97839752aa722492d7
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-05-31T11:23:43Z
add debug print
commit 6a2983f390a0c965345e0b6c1ae1879013ba40cb
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-06-01T02:39:45Z
fix typo
commit 3307c6f2b978d0fc30bea132cef15323e69e98f0
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-06-01T06:26:33Z
add more debug msg
commit e306d4f58036e3088c1ab4f343f186c4df29304d
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-06-01T06:32:38Z
add white space after comma
commit 33100553964d7502ce2143f75762f4c3d39056b0
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-06-01T07:43:55Z
add try catch to find which string failed ci
commit f6fc200e81c2d563e6156de036e41b36f87938b0
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-06-01T09:03:41Z
fix traceback type mismatch
commit bf26dbed1661d1a1155a9fbb892c8da8c03f857e
Author: æ±ªèµ«æ¬ <[email protected]>
Date: 2017-06-01T09:08:52Z
whitespace fitting
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
