[ 
https://issues.apache.org/jira/browse/LIVY-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061530#comment-17061530
 ] 

Simon Skoczylas commented on LIVY-527:
--------------------------------------

Does not work for me either. Using Livy 0.7 with Spark 2.4.4

Tried to send different request bodies:

 
{code:java}
{"kind": "pyspark", "code": "", "cursor": 0}
{code}
 
{code:java}
{"kind": "pyspark", "code": "", "cursor": 1}
{code}
{code:java}
{"kind": "pyspark", "code": "imp", "cursor": 3}
{code}
{code:java}
{"kind": "pyspark", "code": "import ", "cursor": 6}
{code}
{code:java}
{"kind": "pyspark", "code": "import ", "cursor": 7}
{code}
All result in:

 
{code:java}
{"candidates": []}
{code}
I don't understand what the completion is able to complete for Python at all...

 

Does cursor start with 0 or 1?

 

And the description of the issue says "I found the function complete of class 
PythonInterpreter is Empty implementation" ... so it is not implemeted for 
Python? If not, will it be implemented at some day?

It seems, that there is only a test for completion with a scala session ...

 

{{integration-test/src/test/scala/org/apache/livy/test/InteractiveIT.scala}}

 
{code:java}
s.complete("str.", "scala", 4).verifyContaining(List("compare", 
"contains")){code}
 

 

> The Completed interface(/sessions/{sessionId}/completion) doesn't work when 
> kind=pysaprk.
> -----------------------------------------------------------------------------------------
>
>                 Key: LIVY-527
>                 URL: https://issues.apache.org/jira/browse/LIVY-527
>             Project: Livy
>          Issue Type: Bug
>          Components: API, REPL
>    Affects Versions: 0.5.0
>            Reporter: wangqiaoshi
>            Priority: Major
>
> The Completed interface(/sessions/\{sessionId}/completion) doesn't work when 
> kind=pysaprk.
> it always return empty array. I  found  the function complete of  class 
> PythonInterpreter is Empty implementation
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to