[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1861 @felixcheung @minahlee , Sorry my mistake, I has been merged into branch-0.7. @minahlee I notice you make the jira fixversion as 0.8, I add 0.7 as well. --- If your project is set up for it, you

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1861 @felixcheung @minahlee Could any of you help to merge it into branch-0.7 as well ? Since this is only livy interpreter specific, so I don't think it would affect the 0.7 release. --- If your pro

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1861 merging if no more 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 have this feature enabled an

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1861 nope, merging if no more 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 have this feature

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1861 ping @felixcheung any more comments ? --- 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 enab

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1861 The bug in LivySparkSQLInterpreter is caused by this PR. LivySparkSQLInterpreter delegate LivySparkInterpreter to generate InterpreterResult and then convert it to table type. So here since we make

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1861 LGTM. what is the bug in LivySparkSQLInterpreter - should we have a JIRA for it? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as w

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/1861 Tested locally, looks good. --- 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 enable

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1861 @felixcheung I have addressed the comments and also fix one bug in LivySparkSQLInterpreter, and update the screenshot of testing in PR description. --- If your project is set up for it, you can

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1861 @prabhjyotsingh @felixcheung Please help 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