You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2023/01/12 17:01:00 UTC

[jira] [Updated] (IGNITE-18542) Remove duplicate server-side classes from Meta Storage

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

Aleksandr Polovtcev updated IGNITE-18542:
-----------------------------------------
    Description: Before https://issues.apache.org/jira/browse/IGNITE-18413 , we had a separate server and client parts of Meta Storage. These parts were fully independent and had to declare very similar classes (like Entry, Value, Operation, etc). Since this separation has been removed, we don't need to have these duplicates.  (was: Before https://issues.apache.org/jira/browse/IGNITE-18413 , we had a separate server and client parts of Meta Storage. These parts were fully independent and had to declare very similar classes (like Entry, Value, Operation, etc). Since this separation has been removed, we don't need to have these duplicates)

> Remove duplicate server-side classes from Meta Storage
> ------------------------------------------------------
>
>                 Key: IGNITE-18542
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18542
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Before https://issues.apache.org/jira/browse/IGNITE-18413 , we had a separate server and client parts of Meta Storage. These parts were fully independent and had to declare very similar classes (like Entry, Value, Operation, etc). Since this separation has been removed, we don't need to have these duplicates.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)