[ 
https://issues.apache.org/jira/browse/LIVY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jianzhen Wu updated LIVY-899:
-----------------------------
    Description: 
In REST API, ReplDriver would broadcast ReplState to RSCClient when handling 
the ReplJobRequest in stateChangedCallback function.
!image-2022-11-15-20-42-01-214.png|width=242,height=200!
But in Thrift service, the RSCDriver does not broadcast ReplState to RSCClient 
when handling JobRequest.
!image-2022-11-15-20-42-25-472.png|width=241,height=199!

I would like to discuss with you how to resolve this issue.

 

Here's what I think.

 

!image-2022-11-15-20-48-54-653.png|width=228,height=136!

 

 

 

  was:
In REST API, ReplDriver would broadcast ReplState to RSCClient when handling 
the ReplJobRequest in stateChangedCallback function.
!image-2022-11-15-20-42-01-214.png|width=242,height=200!
But in Thrift service, the RSCDriver does not broadcast ReplState to RSCClient 
when handling JobRequest.
!image-2022-11-15-20-42-25-472.png|width=241,height=199!


> The state of interactive session is always idle when using thrift protocol.
> ---------------------------------------------------------------------------
>
>                 Key: LIVY-899
>                 URL: https://issues.apache.org/jira/browse/LIVY-899
>             Project: Livy
>          Issue Type: Bug
>          Components: Thriftserver
>    Affects Versions: 0.8.0
>            Reporter: Jianzhen Wu
>            Assignee: Marco Gaido
>            Priority: Major
>         Attachments: image-2022-11-15-20-42-01-214.png, 
> image-2022-11-15-20-42-25-472.png, image-2022-11-15-20-48-54-653.png
>
>
> In REST API, ReplDriver would broadcast ReplState to RSCClient when handling 
> the ReplJobRequest in stateChangedCallback function.
> !image-2022-11-15-20-42-01-214.png|width=242,height=200!
> But in Thrift service, the RSCDriver does not broadcast ReplState to 
> RSCClient when handling JobRequest.
> !image-2022-11-15-20-42-25-472.png|width=241,height=199!
> I would like to discuss with you how to resolve this issue.
>  
> Here's what I think.
>  
> !image-2022-11-15-20-48-54-653.png|width=228,height=136!
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to