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

[Radim Vansa (JIRA)]

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

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

If you change the fields/marshalling of the entities, yes, you'll have issues. But as an user I'd expect that adding a completely new entity to my schema doesn't blow the app up, and I'd prefer to keep it implemented that way.

My feeling is that hashing (assuming non-byzantine* deployments) makes conflicts so rare that a config option to revert to current behaviour would be sufficient. And if the name is too long *and* has conflicts, the user is simply out of luck. The only thing I'd do is telling user that he has a conflict on the node where we can detect it.

* I hope that we're past the multi-tenancy attempts where we'd expect the other deployment stealing data from cache through generating conflicting hashes on region names, right?

> Handle long qualified region names more effectively
> ---------------------------------------------------
>
>                 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)