[jira] [Commented] (LIVY-616) Livy Server discovery
[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900602#comment-16900602 ] Saisai Shao commented on LIVY-616: -- [~oshevchenko] you can either push an empty commit or reopen the PR to trigger travis test. I'm curious about the scenarios of this proposal. Seems like you don't want to maintain the Livy address in client side, instead asking ZK to get Livy server address. I can see there's some advantages with this proposal, but instead you have to maintain ZK address, what's difference between maintaining either? Typically server discovery mechanism is mainly used in HA scenario, where you can get the active master address from ZK, but current Livy doesn't support HA. So IMHO, I don't see it super useful for now. > Livy Server discovery > - > > Key: LIVY-616 > URL: https://issues.apache.org/jira/browse/LIVY-616 > Project: Livy > Issue Type: Improvement > Components: Server >Reporter: Oleksandr Shevchenko >Priority: Major > Attachments: Livy Server discovery spec.pdf > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, there isn't a way to get Livy Server URI by the client without > setting Livy address explicitly to livy.conf. A client should set > "livy.server.host" variable and then get it via LivyConf. The same behavior > if you want to use Livy with Zeppelin, we need to set "zeppelin.livy.url". It > very inconvenient when we install Livy packages on couple nodes and don't > know where exactly Livy Server will be started e.g. by Ambari or Cloudera > Manager. Also, in this case, we need to have Livy configuration files on a > node where we want to get Livy address. > It will be very helpful if we will add Livy Server address to Zookeeper and > expose API for clients to get Livy URL to use it in client code for REST > calls. > Livy already supports state saving in Zookeeper but I don't see that we store > Livy server address somewhere. Before starting investigating and > implementation I want to ask here about this. > Please, correct me if I missed something. > Any comments will be highly appreciated! -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-631) Implement GetQueryId metadata operation
Yiheng Wang created LIVY-631: Summary: Implement GetQueryId metadata operation Key: LIVY-631 URL: https://issues.apache.org/jira/browse/LIVY-631 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support GetSchemas metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (LIVY-631) Implement GetQueryId metadata operation
[ https://issues.apache.org/jira/browse/LIVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiheng Wang updated LIVY-631: - Description: We should support GetQueryId metadata operation in Livy thrift server. (was: We should support GetSchemas metadata operation in Livy thrift server.) > Implement GetQueryId metadata operation > --- > > Key: LIVY-631 > URL: https://issues.apache.org/jira/browse/LIVY-631 > Project: Livy > Issue Type: Sub-task > Components: Thriftserver >Reporter: Yiheng Wang >Assignee: Yiheng Wang >Priority: Minor > > We should support GetQueryId metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-629) Implement CancelDelegationToken metadata operation
Yiheng Wang created LIVY-629: Summary: Implement CancelDelegationToken metadata operation Key: LIVY-629 URL: https://issues.apache.org/jira/browse/LIVY-629 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support CancelDelegationToken metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-628) Implement GetDelegationToken metadata operation
Yiheng Wang created LIVY-628: Summary: Implement GetDelegationToken metadata operation Key: LIVY-628 URL: https://issues.apache.org/jira/browse/LIVY-628 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support GetDelegationToken metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-627) Implement GetCrossReference metadata operation
Yiheng Wang created LIVY-627: Summary: Implement GetCrossReference metadata operation Key: LIVY-627 URL: https://issues.apache.org/jira/browse/LIVY-627 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support GetCrossReference metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-626) Implement GetPrimaryKeys metadata operation
Yiheng Wang created LIVY-626: Summary: Implement GetPrimaryKeys metadata operation Key: LIVY-626 URL: https://issues.apache.org/jira/browse/LIVY-626 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support GetPrimaryKeys metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-624) Implement GetColumns metadata operation
Yiheng Wang created LIVY-624: Summary: Implement GetColumns metadata operation Key: LIVY-624 URL: https://issues.apache.org/jira/browse/LIVY-624 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support GetColumns metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-625) Implement GetFunctions metadata operation
Yiheng Wang created LIVY-625: Summary: Implement GetFunctions metadata operation Key: LIVY-625 URL: https://issues.apache.org/jira/browse/LIVY-625 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang We should support GetFunctions metadata operation in Livy thrift server. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (LIVY-622) Implement GetSchemas metadata operation
Yiheng Wang created LIVY-622: Summary: Implement GetSchemas metadata operation Key: LIVY-622 URL: https://issues.apache.org/jira/browse/LIVY-622 Project: Livy Issue Type: Sub-task Components: Thriftserver Reporter: Yiheng Wang Assignee: Yiheng Wang -- This message was sent by Atlassian JIRA (v7.6.14#76016)
