[
https://jira.jboss.org/browse/ISPN-579?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus commented on ISPN-579:
------------------------------------
after discussing with Sanne and Manik the following solution is proposed:
- support preload by allowing the users to specify a String to Key mapper as well
(currently the Key2StringMapper does it one way)
- this would implement Key2StringMapper and would be called TwoWayKey2StringMapper
(following hibernate's search terminology)
- if JdbcStringBasedCacheStore is configured with an Key2StringMapper and preload, then an
error is thrown
- if JdbcStringBasedCacheStore is configured with an TwoWayKey2StringMapper then preload
is supported
This way backward compatibility is also supported.
JdbcStringBasedCacheStore preloads data using wrong keys (it
shouldn't preload)
-------------------------------------------------------------------------------
Key: ISPN-579
URL:
https://jira.jboss.org/browse/ISPN-579
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 4.1.0.CR2
Reporter: Sanne Grinovero
Assignee: Mircea Markus
Fix For: 4.1.0.CR3, 4.1.0.Final
It appears that if I happen to configure a JdbcStringBasedCacheStore using preload=true
then cache is preloaded with the values but using the keys in their String form - which is
pointless.
An error should be thrown, like illegal configuration, or a warning logged at runtime
while attempting to load from this implementation and ignoring the load request.
Also documentation is not pointing out this limitation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira