[JBoss JIRA] (ISPN-7108) Use wildcard in methods returning keys
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7108?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-7108:
------------------------------
Status: Open (was: New)
> Use wildcard in methods returning keys
> --------------------------------------
>
> Key: ISPN-7108
> URL: https://issues.jboss.org/browse/ISPN-7108
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Radim Vansa
> Assignee: Radim Vansa
>
> When a command uses generics (that's the case of functional commands), it stores keys in {{Collection<? extends K>}}. That does not work well with {{getAffectedKeys()}} returning {{Set<Object>}} - besides Collection/Set the generic type also cannot match (because returning {{Set<Object>}} means that you can theoretically insert any {{Object}}). Changing that to wildcard deals with this and makes the collection effectively read-only.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (ISPN-7108) Use wildcard in methods returning keys
by Radim Vansa (JIRA)
Radim Vansa created ISPN-7108:
---------------------------------
Summary: Use wildcard in methods returning keys
Key: ISPN-7108
URL: https://issues.jboss.org/browse/ISPN-7108
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Radim Vansa
Assignee: Radim Vansa
When a command uses generics (that's the case of functional commands), it stores keys in {{Collection<? extends K>}}. That does not work well with {{getAffectedKeys()}} returning {{Set<Object>}} - besides Collection/Set the generic type also cannot match (because returning {{Set<Object>}} means that you can theoretically insert any {{Object}}). Changing that to wildcard deals with this and makes the collection effectively read-only.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (ISPN-7107) Unroot InvalidateCommand from RemoteCommand
by Radim Vansa (JIRA)
Radim Vansa created ISPN-7107:
---------------------------------
Summary: Unroot InvalidateCommand from RemoteCommand
Key: ISPN-7107
URL: https://issues.jboss.org/browse/ISPN-7107
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Radim Vansa
Assignee: Radim Vansa
InvalidateCommand and InvalidateL1Command work on multiple keys, while RemoveCommand works on single key. The inheritance is weird and of little benefit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months
[JBoss JIRA] (ISPN-7106) Expiration is not working under some circumstances with AtomicMap
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-7106:
--------------------------------------
Summary: Expiration is not working under some circumstances with AtomicMap
Key: ISPN-7106
URL: https://issues.jboss.org/browse/ISPN-7106
Project: Infinispan
Issue Type: Bug
Components: Core
Environment: AtomicMap, write-skew, transactional
Reporter: Wolf-Dieter Fink
When AtomicMaps are used with writeskew (+ simple versioning) lifespan from the config file is ignored and instead get infinite lifespan for the entries.
The configured default value is used if I any of the following parameters change
- Disable write skew checks
- Use a normal put (not atomic maps)
- Do not start transactions first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 8 months