[jira] [Commented] (IGNITE-12726) Cache names can't be used as part of DistributedMetaStorage keys

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-12726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073613#comment-17073613 ] 

Ignite TC Bot commented on IGNITE-12726:
----------------------------------------

{panel:title=Branch: [pull/7606/head] Base: [master] : Possible Blockers (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5182193]]

{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5180216&buildTypeId=IgniteTests24Java8_RunAll]

> Cache names can't be used as part of DistributedMetaStorage keys
> ----------------------------------------------------------------
>
>                 Key: IGNITE-12726
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12726
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>             Fix For: 2.8.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Issue was discovered during the implementation of IGNITE-12721. Here's a shot version of the description:
>  * local MetaStorage can't handle keys that have more than 64 bytes in their "byte[]" representation. Since DistributedMetaStorage uses it and adds some specific prefixes on top, we have a strict limit on the key length.
> Just to be clear - it just won't work, IGNITE-12721 only adds a valid exception and meaningful error message to the API.
>  
> Recently IGNITE-11987 from [IEP-35] has been merged to master and 2.8 release branch, and it does exactly whats written in the title - adds cache name as a part of the key. So, if you use long cache name in, for example, test called "org.apache.ignite.internal.metric.MetricsConfigurationTest#testConfigRemovedOnCacheRemove", you'll get AssertionErrors in log. By "long" I mean about 50 symbols. This should not happen.
>  
> I see two options here:
>  * leave everything as it is and change keys format;
>  * modify MetaStorage so that it can handle longer keys. I prefer this one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)