[infinispan-issues] [JBoss JIRA] (ISPN-9206) Handle long qualified region names more efficiently

[Radim Vansa (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581642#comment-13581642 ] 

Radim Vansa commented on ISPN-9206:
-----------------------------------

Conflict can be detected locally - you have all the entities that are locally available listed. If there's another node with a list that includes conflicts, it will see the conflict and won't boot. The only situation when you don't detect it (if I am not mistaken) is when you have node1 with deployments A+B, node2 with B+C and there's a conflict between A and C.

I consider hashcodes on by default a safe choice: turning that off is a workaround because the situation might theoretically arise.

> Handle long qualified region names more efficiently
> ---------------------------------------------------
>
>                 Key: ISPN-9206
>                 URL: https://issues.jboss.org/browse/ISPN-9206
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Hibernate Cache
>    Affects Versions: 9.2.2.Final, 9.3.0.Beta1
>            Reporter: Radim Vansa
>            Assignee: Radim Vansa
>
> Hibernate region names are FQCNs, and when the prefix is added this can exceed the 255 byte ByteString limit. Also, it's inefficient to ship such long cache names with each command.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)