Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1067
done in 97f25e2
---
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
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1067
cherry-picking to branch-0.6 fails with merge conflicts as master and
branch-0.6 diverged
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1067
Thank you guys for the prompt reviews!
@Leemoonsoo agree on API change and I'm glad to have it merged in 0.6,
updated JIRA
@minahlee review addressed in 3b1ad36
If there is no mor
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1067
I left few notes on documentation and `help() ` function. Looks good to me.
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1067
I saw https://issues.apache.org/jira/browse/ZEPPELIN-1048 marked 0.7.0 as a
fix version.
Not a strong opinion, and i don't think it should be blocker for 0.6
release. But If we're goin
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1067
It is ready to be merged now.
TODOs will be addressed in different PR, after #1063 is merged
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
