[infinispan-issues] [JBoss JIRA] (ISPN-9206) Handle long qualified region names more efficiently
Paul Ferraro (JIRA)
issues at jboss.org
Thu May 24 12:32:00 EDT 2018
[ https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581851#comment-13581851 ]
Paul Ferraro commented on ISPN-9206:
------------------------------------
[~rvansa]
{quote}
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
{quote}
This is not something WF would/should encourage users to do. There is nothing to be gained by multiple deployment versions sharing the same logical 2LC cluster. This is not a use case that we need to consider.
{quote}
2) with prefixes one server may have more deployments than the other
{quote}
This is very true (at least for bare-metal deployments).
{quote}
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?
{quote}
It's entirely feasible that "com.acme.Entity" can be use by multiple deployments, or even by multiple persistent units within a deployment, each with different caching strategies.
> 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)
More information about the infinispan-issues
mailing list