[
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
{*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine its
{*}PageIo#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.
Implementation thoughts:
* For each structure, we reserve a range of 50 types, and then we get about
1310 (65535 / 50) possible structures, which should be enough;
* Somewhere to keep a register of structures to minimize their intersection,
for example, make it look like [Community edition features
list|https://ggsystems.atlassian.net/wiki/spaces/GG/pages/1192198276/Community+edition+features+list].
was:
Problem:
When adding a new heir to the
{*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine its
{*}PageIo#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.
> 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
> {*}org.apache.ignite.internal.pagememory.io.PageIo{*}, we need to determine
> its {*}PageIo#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.
>
> Implementation thoughts:
> * For each structure, we reserve a range of 50 types, and then we get about
> 1310 (65535 / 50) possible structures, which should be enough;
> * Somewhere to keep a register of structures to minimize their intersection,
> for example, make it look like [Community edition features
> list|https://ggsystems.atlassian.net/wiki/spaces/GG/pages/1192198276/Community+edition+features+list].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
