[
https://issues.apache.org/jira/browse/IGNITE-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-17104:
-------------------------------------
Description:
Problem:
When adding a new heir to the "123" class, we need to determine its type, and
at first glance it is not clear how to do this, and when testing, it turns out
that this type is already taken, which is not convenient. It is necessary to
organize a mechanism / methodology for how to do this, since at the moment the
next one from all known ones is simply taken. Also, don't forget that these
types can be added via modules/plugins.
was:Organization of the PageIo#type to prevent crossing.
> Organize the prevention of crossing the field PageIo#type
> ---------------------------------------------------------
>
> Key: IGNITE-17104
> URL: https://issues.apache.org/jira/browse/IGNITE-17104
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> Problem:
> When adding a new heir to the "123" class, we need to determine its type, and
> at first glance it is not clear how to do this, and when testing, it turns
> out that this type is already taken, which is not convenient. It is necessary
> to organize a mechanism / methodology for how to do this, since at the moment
> the next one from all known ones is simply taken. Also, don't forget that
> these types can be added via modules/plugins.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
