[jira] [Updated] (IGNITE-19888) Track observable timestamp on client
[
https://issues.apache.org/jira/browse/IGNITE-19888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-19888:
---
Description:
*Motivation*
The read timestamp for a RO transaction is supposed to be determined by a
client timestamp to linearize transactions.
*Implementation notes*
* The response, which start RO transaction (IGNITE-19887) has to provide a
timestamp.
* Responses, which start SQL, also provide a specific timestamp (if they start
RO internally) (IGNITE-19898 here the concrete method to retrieve timestamp
will be implemented).
* The current server timestamp ({{clock.now()}}) should be added to (except in
the cases above) the transaction response.
* If a server response does not have the timestamp or timestamp is less than
the client already has, do nothing.
* If the time is grater than the client has, the client timestamp should be
updated.
* The timestamp is used to start RO transaction (IGNITE-19887)
*Definition of done*
The timestamp is passed from the server-side to a client. The client just save
the timestamp and send it in each request to server-side.
All client-side created RO transactions should execute in past with timestamp
has been determining by client timestamp.
was:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
* Response, which start RO transaction (IGNITE-19887) has to provide a
timestamp.
* Responses, which start SQL, also might provide a specific timestamp (if they
start RO internally) (IGNITE-19898 here the concrete method to retrieve
timestamp will be implemented).
* Current server timestamp ({{clock.now()}}) should insert to other (except
cases above) transaction responses.
* If a server response does not have the timestamp or timestamp is less than
the client already has, do nothing.
* If the time is grater than the client has, the client timestamp should be
updated.
* The timestamp is used to start RO transaction (IGNITE-19887)
*Definition of done*
The timestamp is passed from the server-side to a client. The client just save
the timestamp and send it in each request to server-side.
All client-side created RO transactions should execute in past with timestamp
has been determining by client timestamp.
> Track observable timestamp on client
>
>
> Key: IGNITE-19888
> URL: https://issues.apache.org/jira/browse/IGNITE-19888
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> *Motivation*
> The read timestamp for a RO transaction is supposed to be determined by a
> client timestamp to linearize transactions.
> *Implementation notes*
> * The response, which start RO transaction (IGNITE-19887) has to provide a
> timestamp.
> * Responses, which start SQL, also provide a specific timestamp (if they
> start RO internally) (IGNITE-19898 here the concrete method to retrieve
> timestamp will be implemented).
> * The current server timestamp ({{clock.now()}}) should be added to (except
> in the cases above) the transaction response.
> * If a server response does not have the timestamp or timestamp is less than
> the client already has, do nothing.
> * If the time is grater than the client has, the client timestamp should be
> updated.
> * The timestamp is used to start RO transaction (IGNITE-19887)
> *Definition of done*
> The timestamp is passed from the server-side to a client. The client just
> save the timestamp and send it in each request to server-side.
> All client-side created RO transactions should execute in past with timestamp
> has been determining by client timestamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19888) Track observable timestamp on client
[
https://issues.apache.org/jira/browse/IGNITE-19888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-19888:
---
Description:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
* Response, which start RO transaction (IGNITE-19887) has to provide a
timestamp.
* Responses, which start SQL, also might provide a specific timestamp (if they
start RO internally) (IGNITE-19898 here the concrete method to retrieve
timestamp will be implemented).
* Current server timestamp ({{clock.now()}}) should insert to other (except
cases above) transaction responses.
* If a server response does not have the timestamp or timestamp is less than
the client already has, do nothing.
* If the time is grater than the client has, the client timestamp should be
updated.
* The timestamp is used to start RO transaction (IGNITE-19887)
*Definition of done*
The timestamp is passed from the server-side to a client. The client just save
the timestamp and send it in each request to server-side.
All client-side created RO transactions should execute in past with timestamp
has been determining by client timestamp.
was:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
* Responses, which start RO transaction (IGNITE-19887) and commit RW
transaction (IGNITE-19886), have to provide a timestamp.
* Responses, which start SQL, also might provide a specific timestamp (if they
start RO internally) (IGNITE-19898 here the concrete method to retrieve
timestamp will be implemented).
* Current server timestamp ({{clock.now()}}) should insert to other (except
cases above) transaction responses.
* If a server response does not have the timestamp or timestamp is less than
the client already has, do nothing.
* If the time is grater than the client has, the client timestamp should be
updated.
* The timestamp is used to start RO transaction (IGNITE-19887)
*Definition of done*
The timestamp is passed from the server-side to a client. The client just save
the timestamp and send it in each request to server-side.
All client-side created RO transactions should execute in past with timestamp
has been determining by client timestamp.
> Track observable timestamp on client
>
>
> Key: IGNITE-19888
> URL: https://issues.apache.org/jira/browse/IGNITE-19888
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> *Motivation*
> Read timestamp for RO transaction is supposed to determine with taking into
> client timestamp to linearize client transactions.
> *Implementation notes*
> * Response, which start RO transaction (IGNITE-19887) has to provide a
> timestamp.
> * Responses, which start SQL, also might provide a specific timestamp (if
> they start RO internally) (IGNITE-19898 here the concrete method to retrieve
> timestamp will be implemented).
> * Current server timestamp ({{clock.now()}}) should insert to other (except
> cases above) transaction responses.
> * If a server response does not have the timestamp or timestamp is less than
> the client already has, do nothing.
> * If the time is grater than the client has, the client timestamp should be
> updated.
> * The timestamp is used to start RO transaction (IGNITE-19887)
> *Definition of done*
> The timestamp is passed from the server-side to a client. The client just
> save the timestamp and send it in each request to server-side.
> All client-side created RO transactions should execute in past with timestamp
> has been determining by client timestamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19888) Track observable timestamp on client
[
https://issues.apache.org/jira/browse/IGNITE-19888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-19888:
---
Description:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
* Responses, which start RO transaction (IGNITE-19887) and commit RW
transaction (IGNITE-19886), have to provide a timestamp.
* Responses, which start SQL, also might provide a specific timestamp (if they
start RO internally) (IGNITE-19898 here the concrete method to retrieve
timestamp will be implemented).
* Current server timestamp ({{clock.now()}}) should insert to other (except
cases above) transaction responses.
* If a server response does not have the timestamp or timestamp is less than
the client already has, do nothing.
* If the time is grater than the client has, the client timestamp should be
updated.
* The timestamp is used to start RO transaction (IGNITE-19887)
*Definition of done*
The timestamp is passed from the server-side to a client. The client just save
the timestamp and send it in each request to server-side.
All client-side created RO transactions should execute in past with timestamp
has been determining by client timestamp.
was:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
* Responses, which start RO transaction (IGNITE-19887) and commit RW
transaction (IGNITE-19886), have to provide a timestamp.
* Current server timestamp ({{clock.now()}}) should insert to other (except
cases above) transaction responses.
* If a server response does not have the timestamp or timestamp is less than
the client already has, do nothing.
* If the time is grater than the client has, the client timestamp should be
updated.
* The timestamp is used to start RO transaction (IGNITE-19887)
*Definition of done*
The timestamp is passed from the server-side to a client. The client just save
the timestamp and send it in each request to server-side.
All client-side created RO transactions should execute in past with timestamp
has been determining by client timestamp.
> Track observable timestamp on client
>
>
> Key: IGNITE-19888
> URL: https://issues.apache.org/jira/browse/IGNITE-19888
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> *Motivation*
> Read timestamp for RO transaction is supposed to determine with taking into
> client timestamp to linearize client transactions.
> *Implementation notes*
> * Responses, which start RO transaction (IGNITE-19887) and commit RW
> transaction (IGNITE-19886), have to provide a timestamp.
> * Responses, which start SQL, also might provide a specific timestamp (if
> they start RO internally) (IGNITE-19898 here the concrete method to retrieve
> timestamp will be implemented).
> * Current server timestamp ({{clock.now()}}) should insert to other (except
> cases above) transaction responses.
> * If a server response does not have the timestamp or timestamp is less than
> the client already has, do nothing.
> * If the time is grater than the client has, the client timestamp should be
> updated.
> * The timestamp is used to start RO transaction (IGNITE-19887)
> *Definition of done*
> The timestamp is passed from the server-side to a client. The client just
> save the timestamp and send it in each request to server-side.
> All client-side created RO transactions should execute in past with timestamp
> has been determining by client timestamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19888) Track observable timestamp on client
[
https://issues.apache.org/jira/browse/IGNITE-19888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-19888:
---
Summary: Track observable timestamp on client (was: Add tracking of last
observed transaction timestamp to client)
> Track observable timestamp on client
>
>
> Key: IGNITE-19888
> URL: https://issues.apache.org/jira/browse/IGNITE-19888
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> *Motivation*
> Read timestamp for RO transaction is supposed to determine with taking into
> client timestamp to linearize client transactions.
> *Implementation notes*
> * Responses, which start RO transaction (IGNITE-19887) and commit RW
> transaction (IGNITE-19886), have to provide a timestamp.
> * Current server timestamp ({{clock.now()}}) should insert to other (except
> cases above) transaction responses.
> * If a server response does not have the timestamp or timestamp is less than
> the client already has, do nothing.
> * If the time is grater than the client has, the client timestamp should be
> updated.
> * The timestamp is used to start RO transaction (IGNITE-19887)
> *Definition of done*
> The timestamp is passed from the server-side to a client. The client just
> save the timestamp and send it in each request to server-side.
> All client-side created RO transactions should execute in past with timestamp
> has been determining by client timestamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
