You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/10/17 07:41:00 UTC

[jira] [Assigned] (IGNITE-20378) Both clients and embedded nodes should have an ability to see same-actor schema adjustments though RO requests

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

Roman Puchkovskiy reassigned IGNITE-20378:
------------------------------------------

    Assignee:     (was: Roman Puchkovskiy)

>   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
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)