[
https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-9206:
---------------------------------------
+1
I suggested a similar idea to Paul during a chat some months back.
Hashing would not guarantee lack of collisions, but we can test for any collision with
other type names as they are all known upfront, and make adjustments; the important aspect
is that the algorithm be deterministic, so to produce the same "name" on all
nodes.
Since the list of types is well known you could also just sort them, store them in an
array, then use the array index as the identifier. We would still want to print full names
on management operations though, and when logging we'll probably want to know both the
id and the full name.
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)