[
https://jira.jboss.org/browse/ISPN-734?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño commented on ISPN-734:
---------------------------------------
Manik, the problem I see with ConcurrentMap atomic ops when it comes to Collections is the
fact that some can be based on comparison, i.e. replace(). So, replace this list A with
list B is A is still equals to the one in memory. Once you start dealing with larger
lists, this could get quite expensive.
As an example, Redis offers an LPOP operation that return and remove (atomically) the
first element of the List at key.
In Infinispan, you'd have to take the remove element of the list, then call
conditional replace with the new list and if that succeeds, take element removed. If we
offered a Redis operation like this, I wonder if we could provide a more efficient way of
doing this. I also think this might be bordering with OGM / old-PojoCache-style like use
case.
Support of atomic accesses to collection values.
------------------------------------------------
Key: ISPN-734
URL:
https://jira.jboss.org/browse/ISPN-734
Project: Infinispan
Issue Type: Feature Request
Reporter: Tobias Sarnowski
Assignee: Manik Surtani
Redis supports atomic access to values of type list and set. It would be great to have a
similar functionality in infinispan. It enables infinispan to replace some database
architectures completly.
http://code.google.com/p/redis/
"Redis is an advanced key-value store. It is similar to memcached but the dataset is
not volatile, and values can be strings, exactly like in memcached, but also lists, sets,
and ordered sets. All this data types can be manipulated with atomic operations to
push/pop elements, add/remove elements, perform server side union, intersection,
difference between sets, and so forth."
I think sorting is not interesting but the atomic collection accesses are.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira