[jira] [Updated] (IGNITE-16550) Redesign SchemaRegistry to use causality tokens
[
https://issues.apache.org/jira/browse/IGNITE-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16550:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Redesign SchemaRegistry to use causality tokens
> ---
>
> Key: IGNITE-16550
> URL: https://issues.apache.org/jira/browse/IGNITE-16550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Denis Chudov
>Priority: Major
> Labels: ignite-3
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
> the reason all method do not apply a token and work synchronously.
> After the redesign part of the methods should be removed
> (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
> should entirely depend on causality.
> Possibly the new methods will return futures.
> UPD:
> It was decided that in the current ticket it's worth to decouple Schema logic
> from the {{TableManager}} and create a new manager called {{SchemaManager}},
> so we can integrate causality tokens logic to the {{SchemaManager}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16550) Redesign SchemaRegistry to use causality tokens
[
https://issues.apache.org/jira/browse/IGNITE-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-16550:
-
Description:
SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
the reason all method do not apply a token and work synchronously.
After the redesign part of the methods should be removed
(SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
should entirely depend on causality.
Possibly the new methods will return futures.
UPD:
It was decided that in the current ticket it's worth to decouple Schema logic
from the {{TableManager}} and create a new manager called {{SchemaManager}},
so we can integrate causality tokens logic to the {{SchemaManager}}
was:
SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
the reason all method do not apply a token and work synchronously.
After the redesign part of the methods should be removed
(SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
should entirely depend on causality.
Possibly the new methods will return futures.
UPD:
It was decided, that in the current ticket it's worth to decouple Schema logic
from the {{TableManager}} and create a new manager called {{SchemaManager}},
so we can integrate causality tokens logic to the {{SchemaManager}}
> Redesign SchemaRegistry to use causality tokens
> ---
>
> Key: IGNITE-16550
> URL: https://issues.apache.org/jira/browse/IGNITE-16550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
> the reason all method do not apply a token and work synchronously.
> After the redesign part of the methods should be removed
> (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
> should entirely depend on causality.
> Possibly the new methods will return futures.
> UPD:
> It was decided that in the current ticket it's worth to decouple Schema logic
> from the {{TableManager}} and create a new manager called {{SchemaManager}},
> so we can integrate causality tokens logic to the {{SchemaManager}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16550) Redesign SchemaRegistry to use causality tokens
[
https://issues.apache.org/jira/browse/IGNITE-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-16550:
-
Description:
SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
the reason all method do not apply a token and work synchronously.
After the redesign part of the methods should be removed
(SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
should entirely depend on causality.
Possibly the new methods will return futures.
UPD:
It was decided, that in the current ticket it's worth to decouple Schema logic
from the {{TableManager}} and create a new manager called {{SchemaManager}},
so we can integrate causality tokens logic to the {{SchemaManager}}
was:
SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
the reason all method do not apply a token and work synchronously.
After the redesign part of the methods should be removed
(SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
should entirely depend on causality.
Possibly the new methods will return futures.
> Redesign SchemaRegistry to use causality tokens
> ---
>
> Key: IGNITE-16550
> URL: https://issues.apache.org/jira/browse/IGNITE-16550
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by
> the reason all method do not apply a token and work synchronously.
> After the redesign part of the methods should be removed
> (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others
> should entirely depend on causality.
> Possibly the new methods will return futures.
> UPD:
> It was decided, that in the current ticket it's worth to decouple Schema
> logic from the {{TableManager}} and create a new manager called
> {{SchemaManager}},
> so we can integrate causality tokens logic to the {{SchemaManager}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16550) Redesign SchemaRegistry to use causality tokens
[ https://issues.apache.org/jira/browse/IGNITE-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-16550: --- Epic Link: IGNITE-16362 > Redesign SchemaRegistry to use causality tokens > --- > > Key: IGNITE-16550 > URL: https://issues.apache.org/jira/browse/IGNITE-16550 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by > the reason all method do not apply a token and work synchronously. > After the redesign part of the methods should be removed > (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others > should entirely depend on causality. > Possibly the new methods will return futures. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16550) Redesign SchemaRegistry to use causality tokens
[ https://issues.apache.org/jira/browse/IGNITE-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-16550: --- Labels: ignite-3 (was: ) > Redesign SchemaRegistry to use causality tokens > --- > > Key: IGNITE-16550 > URL: https://issues.apache.org/jira/browse/IGNITE-16550 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by > the reason all method do not apply a token and work synchronously. > After the redesign part of the methods should be removed > (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others > should entirely depend on causality. > Possibly the new methods will return futures. -- This message was sent by Atlassian Jira (v8.20.1#820001)
