Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2908
Oh. This is the same one with my PR #2910. I've checked it's not always a
string type. @zjffdu Could you please check my PR and merge both of them?
---
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2910
@zjffdu @felixcheung Please review it.
---
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2910
[HOTFIX] Avoid trimming from non-string type when loading
InterpreterSetting from file
### What is this PR for?
Fixing bug loading InterpreterSetting from file
### What type of PR i
GitHub user apc999 reopened a pull request:
https://github.com/apache/zeppelin/pull/2900
Alluxio
### What is this PR for?
Zeppelin provides an Alluxio interpreter compiled with Alluxio client
v1.0.0, which was released about two years ago. Alluxio 1.0.0 client will not
wor
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2867
Thanks @felixalbani for contribution. I'm merging it to master and
branch-0.8 if no further comment.
---
Github user gd-asharov commented on the issue:
https://github.com/apache/zeppelin/pull/2867
+1, please merge it
---
Github user iijima-satoshi commented on the issue:
https://github.com/apache/zeppelin/pull/2904
Ok, I will try if it is fixed.
---
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2908
```
I'm not 100% sure when map.get(key) is a StringMap?
```
This is due to the schema changes of interpeter.json, and we need to
support different schemas for backward compatibility.
Felix Cheung created ZEPPELIN-3385:
--
Summary: PySpark interpreter should handle .. for autocomplete
Key: ZEPPELIN-3385
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3385
Project: Zeppelin
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2904
could you rebase then if it is fixed?
---
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2884
I've found a bug in this PR. if the value is not a string, it occurs error.
e.g.
```
"zeppelin.python": {
"name": "zeppelin.python",
"value": "python",
11 matches
Mail list logo