[
https://issues.jboss.org/browse/ISPN-9756?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-9756:
------------------------------------
+1 to use the long version, as the HotRod protocol/client API only works with longs.
Luckily ETags can be pretty much anything, so when we change the HR protocol/API to allow
more complex versions ETags can follow suit.
Improve ETag generation in the REST server
------------------------------------------
Key: ISPN-9756
URL:
https://issues.jboss.org/browse/ISPN-9756
Project: Infinispan
Issue Type: Enhancement
Components: REST
Affects Versions: 9.4.2.Final, 10.0.0.Alpha1
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Priority: Major
Etags, used to support conditional operations on REST are calculated using MurmurHash3
and it is not stored in the metadata but rather calculated on the fly.
A better solution would be to reuse the in-place version generator of Hot Rod (numeric
version)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)