[ https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin.... ] 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? -- This message was sent by Atlassian JIRA (v7.5.0#75005)