[
https://issues.apache.org/jira/browse/IGNITE-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20378:
-------------------------------------
Description:
h3. Motivation
{code:java}
client1.sql(CREATE TABLE t1);
client.beginRO()
client.sql(SELECT * from t1); // Given request should see t1.
...
{code}
However it won't be true by default because we may step back for idle safe time
propagation period that might be greater than delay duration in metadata sync
logic.
h3. Definition of Done
* Both clients and embedded nodes should have an ability to see same-actor
schema adjustments though RO requests.
h3. Implementation Notes
Seems that it's required to adjust observable timestamp within DDL operations
or we may consider setting DD greater than idle safe time propagation period.
was:
h3. Motivation
{code:java}
client1.sql(CREATE TABLE t1);
client.beginRO()
client.sql(SELECT * from t1); // Given request should see t1.
...
{code}
However it won't be true by default because we may step back for idle safe time
propagation period that might be greater than delay duration in metadata sync
logic.
h3. Definition of Done
* Both clients and embedded nodes should have an ability to see same-actor
schema adjustments though RO requests.
h3. Implementation Notes
Seems that it's required to adjust observable timestamp within DDL operations
or we may consider setting up DD greater than idle safe time propagation period.
> Both clients and embedded nodes should have an ability to see same-actor
> schema adjustments though RO requests
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-20378
> URL: https://issues.apache.org/jira/browse/IGNITE-20378
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> {code:java}
> client1.sql(CREATE TABLE t1);
> client.beginRO()
> client.sql(SELECT * from t1); // Given request should see t1.
> ...
> {code}
> However it won't be true by default because we may step back for idle safe
> time propagation period that might be greater than delay duration in metadata
> sync logic.
> h3. Definition of Done
> * Both clients and embedded nodes should have an ability to see same-actor
> schema adjustments though RO requests.
> h3. Implementation Notes
> Seems that it's required to adjust observable timestamp within DDL operations
> or we may consider setting DD greater than idle safe time propagation period.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
