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

[Sanne Grinovero (JIRA)]

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

Sanne Grinovero commented on ISPN-9206:
---------------------------------------

Regarding full/short names, I agree and we recently had this same debate in the management SPIs of Hibernate ORM (those who expose a String - these changed).

Good point about possibly having different deployment versions. Wouldn't that have many more issues though? You can't even guarantee that the same named entities actually have compatible fields, or even point to the same database.

I would expect that to be a user error but you're right on needing to be defensive about it, having just a short id would be poor.

Either way, just hashing the name could potentially suffer from similar problems, it just makes it less likely to manifest in practice.

Would be nice to hear [~pferraro]'s opinion on such strategies, I'm sure he has more experience.



> 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)