[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904937#comment-16904937 ]
Oleksandr Shevchenko edited comment on LIVY-616 at 8/12/19 7:40 AM: -------------------------------------------------------------------- {quote}Yes, I was asking how to use HTTP request directly, do you have a related API? {quote} yes, I use LivyDiscoveryManager API, in this way {code} val discoveryManager = LivyDiscoveryManager(livyConf) val address = discoveryManager.getServerUri() val request = sttp .get(uri"$address/sessions/$sessionId") .response(asJson[LivySessionResponse]) {code} It's client code who want to use Livy REST API directly without LivyClient. was (Author: oshevchenko): {quote} Yes, I was asking how to use HTTP request directly, do you have a related API? {quote} yes, I use LivyDiscoveryManager API, in this way val discoveryManager = LivyDiscoveryManager(livyConf) val address = discoveryManager.getServerUri() val request = sttp .get(uri"$address/sessions/$sessionId") .response(asJson[LivySessionResponse]) It's client code who want to use Livy REST API directly without LivyClient. > 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)