Github user esmevane commented on the issue:
https://github.com/apache/zeppelin/pull/2301
Hello there, @benoyantony - could you update me on where you and your team
wound up with this? I'm working on something which sounds pretty similar and
I'd love to know what you all decided.
Github user benoyantony commented on the issue:
https://github.com/apache/zeppelin/pull/2301
@zjffdu , Thanks for pointing me to ZEPPELIN-1338. I did not know about it.
I believe, the intent is same. I agree that the approach is different. We
wanted to shield the user from
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2301
@benoyantony Did you check ZEPPELIN-1338 ? Your approach seems some kind of
workaround to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user benoyantony commented on the issue:
https://github.com/apache/zeppelin/pull/2301
@Leemoonsoo , Could you please review this feature ?
---
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
