[
https://issues.apache.org/jira/browse/IGNITE-14764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349369#comment-17349369
]
Mirza Aliev commented on IGNITE-14764:
--------------------------------------
LGTM
> Consolidation of managers and metastorage server implementation.
> ----------------------------------------------------------------
>
> Key: IGNITE-14764
> URL: https://issues.apache.org/jira/browse/IGNITE-14764
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexander Lapin
> Assignee: Vladislav Pyatkov
> Priority: Blocker
> Labels: 3.0.0-alpha2, ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After merging meta storage server logic few bugs of ignition start, table
> creation and atomic operations were revealed. Some of them will be specified
> in greater detail and fixed within corresponding tickets:
> * https://issues.apache.org/jira/browse/IGNITE-14756 - NPE on reading
> tableConfiguration from ConfigurationManager within SchemaManager
> * https://issues.apache.org/jira/browse/IGNITE-14762 - Leader refresh
> sometimes blocks indefinitely
> * https://issues.apache.org/jira/browse/IGNITE-14290 Includes INT32, INT64,
> etc support
> Other issues will be fixed within given ticket:
> * Incoorect usage of appliedRevision as watch revision. appliedRevision + 1
> should be used instead. That produced Mutilple AssertionErros.
> * Incorrect masterKey invoke condition in DistributedConfigurationStorage:
> Conditions.revision(MASTER_KEY).eq(ver.get()) That won't work if there's no
> MASTER_KEY, which is always true on initial node startup without PDS
> * Schema descriptor serialization issues
> * String type is unsupported.
> * Incorrect assignment calculation based on Vault, TableConfiguration from
> ConfigurationManager will be used instead.
> * Empty metastorageNodes configuration property. Default value will be added.
> * Incorrect tblId parsing in SchemaManager
> * and few more.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
