[jira] [Updated] (LIVY-646) Travis failed on rsc unit tests: RSCClient instance stopped

[ https://issues.apache.org/jira/browse/LIVY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-646: Summary: Travis failed on rsc unit tests: RSCClient instance stopped (was: Travis failed on rsc unit tests)

[jira] [Updated] (LIVY-646) Travis failed on rsc unit tests: RSCClient instance stopped

[ https://issues.apache.org/jira/browse/LIVY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-646: Description:    Running org.apache.livy.rsc.TestSparkClient Tests run: 19, Failures: 0, Errors: 1,

[jira] [Updated] (LIVY-656) Travis failed on "start a repl session using the rsc"

[ https://issues.apache.org/jira/browse/LIVY-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-656: Description: - start a repl session using the rsc *** FAILED *** (37 seconds, 374 milliseconds)

[jira] [Commented] (LIVY-657) Travis failed on should not create sessions with duplicate names

[ https://issues.apache.org/jira/browse/LIVY-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920651#comment-16920651 ] runzhiwang commented on LIVY-657: - I'm working on it. > Travis failed on should not create sessions with

[jira] [Created] (LIVY-657) Travis failed on should not create sessions with duplicate names

runzhiwang created LIVY-657: --- Summary: Travis failed on should not create sessions with duplicate names Key: LIVY-657 URL: https://issues.apache.org/jira/browse/LIVY-657 Project: Livy Issue Type:

[jira] [Created] (LIVY-656) Travis failed on "start a repl session using the rsc"

runzhiwang created LIVY-656: --- Summary: Travis failed on "start a repl session using the rsc" Key: LIVY-656 URL: https://issues.apache.org/jira/browse/LIVY-656 Project: Livy Issue Type: Bug

[jira] [Created] (LIVY-655) Travis failed on “testConnectToRunningContext”

runzhiwang created LIVY-655: --- Summary: Travis failed on “testConnectToRunningContext” Key: LIVY-655 URL: https://issues.apache.org/jira/browse/LIVY-655 Project: Livy Issue Type: Bug

[jira] [Updated] (LIVY-655) Travis failed on “testConnectToRunningContext”

[ https://issues.apache.org/jira/browse/LIVY-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-655: Description: Tests run: 19, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 70.658 sec <<< FAILURE! - in

[jira] [Commented] (LIVY-655) Travis failed on “testConnectToRunningContext”

[ https://issues.apache.org/jira/browse/LIVY-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918304#comment-16918304 ] runzhiwang commented on LIVY-655: - I'm working on it. > Travis failed on “testConnectToRunningContext” >

[jira] [Commented] (LIVY-636) Unable to create interactive session with additional JAR in spark.driver.extraClassPath

[ https://issues.apache.org/jira/browse/LIVY-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918305#comment-16918305 ] runzhiwang commented on LIVY-636: - Hi [~ishitavirmani] Do you have any updates ? > Unable to create

[jira] [Created] (LIVY-659) Travis failed on "can kill spark-submit while it's running"

runzhiwang created LIVY-659: --- Summary: Travis failed on "can kill spark-submit while it's running" Key: LIVY-659 URL: https://issues.apache.org/jira/browse/LIVY-659 Project: Livy Issue Type: Bug

[jira] [Commented] (LIVY-659) Travis failed on "can kill spark-submit while it's running"

[ https://issues.apache.org/jira/browse/LIVY-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922336#comment-16922336 ] runzhiwang commented on LIVY-659: - I‘m working on it. > Travis failed on "can kill spark-submit while it's

[jira] [Created] (LIVY-665) Travis failed on "should not honor impersonation requests"

runzhiwang created LIVY-665: --- Summary: Travis failed on "should not honor impersonation requests" Key: LIVY-665 URL: https://issues.apache.org/jira/browse/LIVY-665 Project: Livy Issue Type: Bug

[jira] [Issue Comment Deleted] (LIVY-661) POST /sessions API - Conf parameters

[ https://issues.apache.org/jira/browse/LIVY-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-661: Comment: was deleted (was: I'm working on it) > POST /sessions API - Conf parameters >

[jira] [Updated] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: Support query a lot of data. (was: Collect a part of partition to the driver by batch to avoid

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930215#comment-16930215 ] runzhiwang edited comment on LIVY-667 at 9/18/19 8:21 AM: -- There are several

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930215#comment-16930215 ] runzhiwang edited comment on LIVY-667 at 9/18/19 8:17 AM: -- There are several

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930215#comment-16930215 ] runzhiwang edited comment on LIVY-667 at 9/18/19 8:16 AM: -- There are several

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930215#comment-16930215 ] runzhiwang edited comment on LIVY-667 at 9/18/19 12:31 PM: --- There are several

[jira] [Updated] (LIVY-667) Collecting a part of partition to the driver by batch

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: Collecting a part of partition to the driver by batch (was: support query partition by batch) >

[jira] [Updated] (LIVY-667) Collect a part of partition to the driver by batch to avoid OOM

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: Collect a part of partition to the driver by batch to avoid OOM (was: Collecting a part of

[jira] [Updated] (LIVY-667) support query big partition

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: support query big partition (was: Don't support query big partition) > support query big

[jira] [Updated] (LIVY-667) support query big partition by batch

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: support query big partition by batch (was: support query big partition) > support query big

[jira] [Updated] (LIVY-667) support query partition by batch

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: support query partition by batch (was: support query big partition by batch) > support query

[jira] [Updated] (LIVY-667) Collecting a part of partition to the driver by batch to avoid OOM

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-667: Summary: Collecting a part of partition to the driver by batch to avoid OOM (was: Collecting a part of

[jira] [Commented] (LIVY-667) Don't support query big partition

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930215#comment-16930215 ] runzhiwang commented on LIVY-667: - I'm working on it > Don't support query big partition >

[jira] [Created] (LIVY-667) Don't support query big partition

runzhiwang created LIVY-667: --- Summary: Don't support query big partition Key: LIVY-667 URL: https://issues.apache.org/jira/browse/LIVY-667 Project: Livy Issue Type: Bug Components:

[jira] [Commented] (LIVY-661) POST /sessions API - Conf parameters

[ https://issues.apache.org/jira/browse/LIVY-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930210#comment-16930210 ] runzhiwang commented on LIVY-661: - I'm working on it > POST /sessions API - Conf parameters >

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930215#comment-16930215 ] runzhiwang edited comment on LIVY-667 at 9/20/19 3:13 AM: -- hi,[~jerryshao], 

[jira] [Commented] (LIVY-721) Distributed Session ID Generation

[ https://issues.apache.org/jira/browse/LIVY-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986605#comment-16986605 ] runzhiwang commented on LIVY-721: - I am working on it. > Distributed Session ID Generation >

[jira] [Commented] (LIVY-722) Session Allocation with Consistent Hashing

[ https://issues.apache.org/jira/browse/LIVY-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986606#comment-16986606 ] runzhiwang commented on LIVY-722: - I'm working on it > Session Allocation with Consistent Hashing >

[jira] [Commented] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.

[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990343#comment-16990343 ] runzhiwang commented on LIVY-727: - I‘m working on it. > Session state always be idle though the yarn

[jira] [Created] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.

runzhiwang created LIVY-727: --- Summary: Session state always be idle though the yarn application has been killed after restart livy. Key: LIVY-727 URL: https://issues.apache.org/jira/browse/LIVY-727

[jira] [Updated] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.

[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-727: Description: # Set livy.server.recovery.mode=recovery, and create a session in yarn-cluster # Restart

[jira] [Updated] (LIVY-729) Livy should not recover the killed session

[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-729: Attachment: image-2019-12-18-08-56-46-925.png > Livy should not recover the killed session >

[jira] [Created] (LIVY-729) Livy should not recover the killed session

runzhiwang created LIVY-729: --- Summary: Livy should not recover the killed session Key: LIVY-729 URL: https://issues.apache.org/jira/browse/LIVY-729 Project: Livy Issue Type: Bug

[jira] [Updated] (LIVY-729) Livy should not recover the killed session

[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-729: Description: How to reproduce the problem: 1. !image-2019-12-18-08-56-46-925.png! > Livy should not

[jira] [Commented] (LIVY-729) Livy should not recover the killed session

[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998710#comment-16998710 ] runzhiwang commented on LIVY-729: - working on it > Livy should not recover the killed session >

[jira] [Updated] (LIVY-729) Livy should not recover the killed session

[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-729: Description: Follows are steps to reproduce the problem: # Set livy.server.recovery.mode=recovery, and

[jira] [Updated] (LIVY-729) Livy should not recover the killed session

[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-729: Description: Follows are steps to reproduce the problem: # Set livy.server.recovery.mode=recovery, and

[jira] [Updated] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.

[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-727: Description: # Set livy.server.recovery.mode=recovery, and create a session in yarn-cluster # Restart

[jira] [Commented] (LIVY-720) NoSuchElementException caused when reading from hdfs submitted via livy programmatic api

[ https://issues.apache.org/jira/browse/LIVY-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987467#comment-16987467 ] runzhiwang commented on LIVY-720: - I will work on it recently.  > NoSuchElementException caused when

[jira] [Updated] (LIVY-699) [LIVY-699][Thrift] Fix getColumnTypeName cannot return decimal, timestamp and date

[ https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-699: Summary: [LIVY-699][Thrift] Fix getColumnTypeName cannot return decimal, timestamp and date (was: Support

[jira] [Updated] (LIVY-699) [LIVY-699][Thrift] Fix getColumnTypeName cannot return decimal, timestamp and date

[ https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-699: Description: Follows are steps to reproduce the problem: # create table test(id decimal). #

[jira] [Updated] (LIVY-699) [LIVY-699][Thrift] Fix getColumnTypeName cannot return decimal, timestamp and date

[ https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-699: Description: Follows are steps to reproduce the problem: # {{create table test(id decimal)}}. #

[jira] [Created] (LIVY-699) Support DateType: decimal, timestamp, date

runzhiwang created LIVY-699: --- Summary: Support DateType: decimal, timestamp, date Key: LIVY-699 URL: https://issues.apache.org/jira/browse/LIVY-699 Project: Livy Issue Type: Bug Affects

[jira] [Updated] (LIVY-699) [LIVY-699][THRIFT] Fix resultSet.getBigDecimal throw java.sql.SQLException: Illegal conversion

[ https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-699: Summary: [LIVY-699][THRIFT] Fix resultSet.getBigDecimal throw java.sql.SQLException: Illegal conversion

[jira] [Updated] (LIVY-699) [LIVY-699][THRIFT] Fix resultSet.getBigDecimal throw java.sql.SQLException: Illegal conversion

[ https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-699: Description: LIVY-699[THRIFT] Fix resultSet.getBigDecimal throw java.sql.SQLException: Illegal conversion.

[jira] [Updated] (LIVY-699) [LIVY-699][THRIFT] Fix resultSet.getBigDecimal throw java.sql.SQLException: Illegal conversion

[ https://issues.apache.org/jira/browse/LIVY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-699: Description: [LIVY-699][THRIFT] Fix resultSet.getBigDecimal throw java.sql.SQLException: Illegal

[jira] [Updated] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-714: Description: (was:

[jira] [Updated] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-714: Attachment: image-2019-11-20-09-50-52-316.png > Cannot remove the app in leakedAppTags when timeout >

[jira] [Updated] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-714: Description: !image-2019-11-20-09-50-52-316.png! > Cannot remove the app in leakedAppTags when timeout >

[jira] [Updated] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-714: Attachment: bug.png > Cannot remove the app in leakedAppTags when timeout >

[jira] [Created] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

runzhiwang created LIVY-714: --- Summary: Cannot remove the app in leakedAppTags when timeout Key: LIVY-714 URL: https://issues.apache.org/jira/browse/LIVY-714 Project: Livy Issue Type: New Feature

[jira] [Updated] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-714: Description: # var isRemoved = false should be in while(iter.hasNext), otherwise if there are two apps, the

[jira] [Commented] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16977987#comment-16977987 ] runzhiwang commented on LIVY-714: - I'm working on it. > Cannot remove the app in leakedAppTags when

[jira] [Updated] (LIVY-711) jdk8 cause travis failed

[ https://issues.apache.org/jira/browse/LIVY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-711: Summary: jdk8 cause travis failed (was: travis failed) > jdk8 cause travis failed >

[jira] [Created] (LIVY-711) travis failed

runzhiwang created LIVY-711: --- Summary: travis failed Key: LIVY-711 URL: https://issues.apache.org/jira/browse/LIVY-711 Project: Livy Issue Type: New Feature Reporter: runzhiwang

[jira] [Updated] (LIVY-711) Travis fails to build on Ubuntu16.04

[ https://issues.apache.org/jira/browse/LIVY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-711: Attachment: image-2019-11-12-14-25-37-189.png > Travis fails to build on Ubuntu16.04 >

[jira] [Updated] (LIVY-711) Travis fails to build on Ubuntu16.04

[ https://issues.apache.org/jira/browse/LIVY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-711: Summary: Travis fails to build on Ubuntu16.04 (was: Fails to build on Travis CI (Xenial)) > Travis fails

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935497#comment-16935497 ] runzhiwang edited comment on LIVY-667 at 9/23/19 6:26 AM: -- [~mgaido] Because of

[jira] [Comment Edited] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935497#comment-16935497 ] runzhiwang edited comment on LIVY-667 at 9/23/19 1:21 AM: -- [~mgaido] Because of

[jira] [Commented] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935497#comment-16935497 ] runzhiwang commented on LIVY-667: - [~mgaido] Because of the limited memory and huge size of user data,

[jira] [Created] (LIVY-697) rsc client cannot resolve the hostname of driver in yarn-cluster mode

runzhiwang created LIVY-697: --- Summary: rsc client cannot resolve the hostname of driver in yarn-cluster mode Key: LIVY-697 URL: https://issues.apache.org/jira/browse/LIVY-697 Project: Livy Issue

[jira] [Commented] (LIVY-697) Rsc client cannot resolve the hostname of driver in yarn-cluster mode

[ https://issues.apache.org/jira/browse/LIVY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950215#comment-16950215 ] runzhiwang commented on LIVY-697: - working on it > Rsc client cannot resolve the hostname of driver in

[jira] [Updated] (LIVY-697) Rsc client cannot resolve the hostname of driver in yarn-cluster mode

[ https://issues.apache.org/jira/browse/LIVY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-697: Summary: Rsc client cannot resolve the hostname of driver in yarn-cluster mode (was: rsc client cannot

[jira] [Updated] (LIVY-732) A Common Zookeeper Wrapper Utility

[ https://issues.apache.org/jira/browse/LIVY-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-732: Description: Currently, the utilities of zookeeper mixed with ZooKeeperStateStore. To use the utility of

[jira] [Updated] (LIVY-735) Fix RPC Channel Closed When Multi Clients Connect to One Driver

[ https://issues.apache.org/jira/browse/LIVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-735: Description: Currently, the driver tries to support communicating with multi-clients, by registering each

[jira] [Updated] (LIVY-732) A Common Zookeeper Wrapper Utility

[ https://issues.apache.org/jira/browse/LIVY-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-732: Description: Currently, the utilities of zookeeper mixed with ZooKeeperStateStore. To use the utility of

[jira] [Commented] (LIVY-730) Travis failed because of RSCClient instance stopped

[ https://issues.apache.org/jira/browse/LIVY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999628#comment-16999628 ] runzhiwang commented on LIVY-730: - I'm working on it. > Travis failed because of RSCClient instance

[jira] [Created] (LIVY-730) Travis failed because of RSCClient instance stopped

runzhiwang created LIVY-730: --- Summary: Travis failed because of RSCClient instance stopped Key: LIVY-730 URL: https://issues.apache.org/jira/browse/LIVY-730 Project: Livy Issue Type: Bug

[jira] [Updated] (LIVY-732) A Common Zookeeper Wrapper Utility

[ https://issues.apache.org/jira/browse/LIVY-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-732: Description: Currently, the utility of zookeeper mixed with ZooKeeperStateStore.  > A Common Zookeeper

[jira] [Updated] (LIVY-732) A Common Zookeeper Wrapper Utility

[ https://issues.apache.org/jira/browse/LIVY-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-732: Description: Currently, the utility of zookeeper mixed with ZooKeeperStateStore, and it's weird. (was:

[jira] [Updated] (LIVY-720) NoSuchElementException caused when reading from hdfs submitted via livy programmatic api

[ https://issues.apache.org/jira/browse/LIVY-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-720: Attachment: FailingLivySparkJob.zip > NoSuchElementException caused when reading from hdfs submitted via

[jira] [Comment Edited] (LIVY-720) NoSuchElementException caused when reading from hdfs submitted via livy programmatic api

[ https://issues.apache.org/jira/browse/LIVY-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987467#comment-16987467 ] runzhiwang edited comment on LIVY-720 at 12/10/19 6:56 AM: --- [~steviej08] Hi, I

[jira] [Updated] (LIVY-721) Distributed Session ID Generation

[ https://issues.apache.org/jira/browse/LIVY-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-721: Description: # When generate unique session id with multiple-active HA mode. First, get the distributed

[jira] [Updated] (LIVY-721) Distributed Session ID Generation

[ https://issues.apache.org/jira/browse/LIVY-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated LIVY-721: Description: # When generate unique session id with multiple-active HA mode. First, get the distributed