You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2022/04/05 10:32:00 UTC
[jira] [Updated] (IGNITE-16796) Rename is broken in configuration & other minor issues
[ https://issues.apache.org/jira/browse/IGNITE-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Bessonov updated IGNITE-16796:
-----------------------------------
Summary: Rename is broken in configuration & other minor issues (was: Rename is broken in configuration)
> Rename is broken in configuration & other minor issues
> ------------------------------------------------------
>
> Key: IGNITE-16796
> URL: https://issues.apache.org/jira/browse/IGNITE-16796
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha4
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> Rename changes "name" field in an immutable object, this shouldn't happen.
>
> There are also few more issues that I'd like to address:
> * configuration values serialization wouldn't work for string with non-ascii characters because of wrong "size" calculation
> * signatures of ConfigurationNotificationEvent#config and ConfigurationNotificationEvent#name are flawed and need to be refined a bit
> * InjectName is not used where it needs to be used
--
This message was sent by Atlassian Jira
(v8.20.1#820001)