[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=13581420#comment-13581420 ] 

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

[~sannegrinovero] Are you sure that the list will be equal on all nodes? I can imagine 
1) app having two different versions clustered together - at least temporarily during roll out
2) with prefixes one server may have more deployments than the other

For debugging purposes I'd keep the last segment of the region name (simple name of the class) - even in production. Why do you need the management operations to expose **full** names? I would consider cache names an implementation detail. IMO the last segment should make it distinguishable enough.

We'd need to handle different configuration options a bit differently - right now for specific overrides we use o.h.cache.infinispan.*deployment*#*com.acme.Entity*.cfg - is the deployment really needed there? Isn't the persistence.xml (or spring properties or whatever file you provide) always scoped to the deployment anyway?

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