[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1960 LGTM --- 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 the

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1960 Thank you for quick response! Let me merge this. --- 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

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 Yes, the PR is ready. CI failure is not relevant. Please help include it in 0.7 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1960 @zjffdu @del680202 Is this ready? :) --- 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 ena

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 @del680202 Thanks for checking. --- 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 a

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user del680202 commented on the issue: https://github.com/apache/zeppelin/pull/1960 I test the same query by ``%jdbc``, I got the same result with ``%spark.sql`` ![2017-02-01 10 41 21](https://cloud.githubusercontent.com/assets/3747345/22492061/1f38dd84-e86b-11e6-8bed-90330

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user del680202 commented on the issue: https://github.com/apache/zeppelin/pull/1960 @zjffdu I had try to query sample table by ``%spark.sql``. Alert message is not red but it works. ![2017-02-01 10 32 04](https://cloud.githubusercontent.com/assets/3747345/22491

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 @del680202 Can you try this on `%spark.sql` as well ? I guess `Output exceeds...` may also cause issues in displaying table format data in `%spark.sql` --- If your project is set up for it, you c

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 hmm, right. `LivySparkSQLInterpreter` delegate interpret to `LivySparkInterpreter`. So it is possible to get `Output exceeds...` in `LivySparkSQLInterpreter`. Thanks @del680202 --- If your proj

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user del680202 commented on the issue: https://github.com/apache/zeppelin/pull/1960 Actually, I inject ``LOGGER.info(line)`` into ``parseSQLOutput`` for tracing input. Then I got string at least line in result ``INFO [2017-01-31 16:24:19,584] ({pool-2-thread-5} LivySpa

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 I suspect it is caused by other issues rather than `Output exceeds...`. Because message `Output exceeds...` should be generated after the method `parseSQLOutput` --- If your project is set up for

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 I am not sure whether that would help, because `Output exceeds ...` is generated by zeppelin, not by livy or spark. https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user del680202 commented on the issue: https://github.com/apache/zeppelin/pull/1960 @zjffdu I got error message as below ``` ERROR [2017-01-31 16:34:34,431] ({pool-2-thread-7} LivySparkSQLInterpreter.java[interpret]:143) - Exception in LivySparkSQLInterpreter whil

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 @del680202 Can you paste the full stacktrace ? --- 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 fea

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user del680202 commented on the issue: https://github.com/apache/zeppelin/pull/1960 Oh.. When I test ``%livy.sql`` by my hive table, ``TEXT`` result ``Output exceeds 102400. Truncated.`` causes a failure. --- If your project is set up for it, you can reply to this email and ha

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 lgtm --- 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 the feat

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user del680202 commented on the issue: https://github.com/apache/zeppelin/pull/1960 OK, I will add test cases for this issue --- 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 featur

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 Thanks @del680202 Could you add unit test in `LivySQLInterpreterTest.java`? --- 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 p

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1960 this is odd, we should have test that catches this condition - could you check if we could add to livy interpreter tests for this? --- If your project is set up for it, you can reply to this

[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...

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