I've looked a little deeper and see now my error, those parameters are for
python and java clients (clearly). I forgot there was clients in the code
base. Just wishful thinking on my part I guess...
In any case, I'm still hoping to understand where Livy overhead on queries is
coming from.
Thank you Saisai for your response.
I did have a chance to investigate further and I should give a little
background on why I feel network cost is not the issue:
I added to our application Kylo (http://kylo.io) as an optional spark
server that is used as a replacement for our existing
Hi,
we are trying to build a setup where we have a server that submits jobs
of different users to the Livy server via the REST API. We established a
kerberos server to authenticate against livy, with one superuser that
makes the requests in behalf of the users. But we want to prohibit
the users to
