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

Vladislav Pyatkov updated IGNITE-17659:
---------------------------------------
    Description: 
The _InternalTable#scan_ method has two issues:

1) Cancel scanning does not send a message to served side and does not clear 
cursor, that is opened in server side.
The close message (look at {_}ScanCloseReplicaRequest{_}) should be sent after 
a subscriber is received a last one batch of entries or Subscription#cancel is 
invoked.

2) The API does not work correctly for implicit transaction.
Implicit transaction should be started at the first retrieve batch request is 
sent. The transaction shouldn't be closed until the subscriber reads to the end 
or Subscription#cancel is not invoked.
 

  was:
The _InternalTable#scan_ method has two issues:

1) Cancel scanning does not send a message to served side and does not clear 
cursor, that is opened in server side.
The close message should be sent after a subscriber is received a last one 
batch of entries or Subscription#cancel is invoked.

2) The API does not work correctly for implicit transaction.
Implicit transaction should be started at the first retrieve batch request is 
sent. The transaction shouldn't be closed until the subscriber reads to the end 
or Subscription#cancel is not invoked.


> Table Scan workflow enhancement
> -------------------------------
>
>                 Key: IGNITE-17659
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17659
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> The _InternalTable#scan_ method has two issues:
> 1) Cancel scanning does not send a message to served side and does not clear 
> cursor, that is opened in server side.
> The close message (look at {_}ScanCloseReplicaRequest{_}) should be sent 
> after a subscriber is received a last one batch of entries or 
> Subscription#cancel is invoked.
> 2) The API does not work correctly for implicit transaction.
> Implicit transaction should be started at the first retrieve batch request is 
> sent. The transaction shouldn't be closed until the subscriber reads to the 
> end or Subscription#cancel is not invoked.
>  



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

Reply via email to