Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1124
CI is green now
---
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 felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1124
I think this is a good improvement - left a comment.
---
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 ha
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1124
Thank you @minahlee for prompt review and notice on CI fix, I really
appreciate!
Merging if there is no more discussion
---
If your project is set up for it, you can reply to this email and
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1124
Tested basic functionality. Looks good to me.
CI failure is irrelevant and being taken care of under #1129.
---
If your project is set up for it, you can reply to this email and have you
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1124
reabsed on latest master
ping @khalidhuseynov @minahlee @jongyoul for a review
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1124
re-trigger CI
---
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 th
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1124
Ready to merge, \cc @minahlee @jongyoul for review
---
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 fe
