[JBoss JIRA] (ISPN-2732) Support more efficient operations when value is a collection
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2732?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2732:
--------------------------------
Fix Version/s: (was: 6.0.0.Final)
> Support more efficient operations when value is a collection
> ------------------------------------------------------------
>
> Key: ISPN-2732
> URL: https://issues.jboss.org/browse/ISPN-2732
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Cache
> Reporter: Ray Tsang
> Assignee: Mircea Markus
>
> Support operations such as append, push/pop, etc for being able to store collection/list as value
> Support operation such as slice to retrieve parts of collections.
> Some collections in mind are: Deque, PriorityQueue (heap, sorted list), etc.
> Perhaps expand on Delta and DeltaAware, and as counterparts to AtomicHashMap.
> If using current map interface, maybe something along the line of:
> map.put("key", new AppendDelta("..."));
> map.get("key", new RangeSlice(1, 5));
> or advancedCache.applyDelta(...); and advancedCache.retrieveSlice(...)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (ISPN-2797) Support Query on Caches configured with INVALIDATION mode
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2797?page=com.atlassian.jira.plugin.... ]
Mircea Markus commented on ISPN-2797:
-------------------------------------
The only use case I know about for invalidation caches is as an JPA L2 cache, which wouldn't require querying. Any other situation in which invalidation caches might be needed that you can think of?
> Support Query on Caches configured with INVALIDATION mode
> ---------------------------------------------------------
>
> Key: ISPN-2797
> URL: https://issues.jboss.org/browse/ISPN-2797
> Project: Infinispan
> Issue Type: Feature Request
> Components: Querying
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Labels: stable_embedded_query
> Fix For: 6.0.0.Alpha1
>
>
> This is currently not supported as other nodes won't get a copy of the value, and are consequentially unable to scan annotations or recognize new services which need to be started.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (ISPN-2234) Support a HotRod URL
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2234?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2234:
--------------------------------
Fix Version/s: (was: 6.0.0.Final)
> Support a HotRod URL
> --------------------
>
> Key: ISPN-2234
> URL: https://issues.jboss.org/browse/ISPN-2234
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote protocols
> Reporter: Tristan Tarrant
> Assignee: Galder Zamarreño
> Priority: Minor
> Labels: hackathon
>
> It would be nice to have a HotRod URL format to represent lists of remote servers in a compact and understandable way.
> We could pattern this on MySQL's JDBC URL format as follows:
> {code}hotrod://[host][,host...][:port]/[remoteCacheName]{code}
> or alternatively
> {code}hotrod://[host:port],[host:port].../[remoteCacheName]{code}
> Optionally we could also add support for additional properties appended to the above URLs:
> {code}hotrod://[host][,host...][:port]/[remoteCacheName]?
> propertyName1=propertyValue1&propertyName2=propertyValue2{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months