Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2231
This problem still exist in LivyPySparkBaseInterpreter.java. This file
still use sc._jsc.sc().ui().get().appUIAddress() and %livy.pyspark doesn't
work when using spark 2.2.
---
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2412
@jasper-k
Zeppelin 0.7.2 was released on Jun 12 and this pull got merged to master
on Sep 28. Even Zeppelin 0.7.3 doesn't contain this pull since it was released
on Sep 21. So I think
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2412
@zjffdu Update the PR to what state?
---
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2412
@felixcheung It didn't fail. But when using byte to encode to UTF-8 byte,
CI log can show Chinese correctly.
---
If your project is set up for it, you can reply to this email and have your
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2412
@zjffdu @felixcheung After putting Chinese "ä½ ä½ ä½ ä½ ä½ ä½ å¥½"
directly inside test code, I got the following log in Travis CI test. May be
use UTF8 byte to create inexplic
GitHub user qwemicheal opened a pull request:
https://github.com/apache/zeppelin/pull/2412
[ZEPPELIN-2641] Change encoding to UTF-8 when sending request to Livy
### What is this PR for?
Change encoding of the request sent from Zeppelin to Livy to UTF-8. In this
way, Zeppelin
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2390
@zjffdu The failure most often happen on the third one of Travis CI ,
sometimes the second one or ninth one. I have checked the error log multiple
times and they all have nothing to do
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2390
Finally pass the CI. @zjffdu I have updated the screen shot and could you
share any light on why CI would fail randomly?
---
If your project is set up for it, you can reply to this email
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2390
@zjffdu Unit test merged and the traceback msg concatenated to one string.
During CI testing, the third one would fail randomly with the following
error
Github user qwemicheal commented on the issue:
https://github.com/apache/zeppelin/pull/2390
@zjffdu Unit test added.
---
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
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
11 matches
Mail list logo
