[JBoss JIRA] (ISPN-9699) Cluster member owning no data
by Thomas Segismont (Jira)
Thomas Segismont created ISPN-9699:
--------------------------------------
Summary: Cluster member owning no data
Key: ISPN-9699
URL: https://issues.jboss.org/browse/ISPN-9699
Project: Infinispan
Issue Type: Feature Request
Reporter: Thomas Segismont
Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment.
If you want a node to own no data at all, you could set this property on all declared cached. But this wouldn't work for internal caches anyway (locks, counters).
It would be nice to have a global switch.
This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster:
* there would be no data loss
* the cluster would be back in healthy state faster as no data would be moved around.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-9698) SpringCache doesn't unwrap null values in get(key, valueLoader) overload
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9698?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-9698:
-------------------------------------
Assignee: Katia Aresti
> SpringCache doesn't unwrap null values in get(key, valueLoader) overload
> ------------------------------------------------------------------------
>
> Key: ISPN-9698
> URL: https://issues.jboss.org/browse/ISPN-9698
> Project: Infinispan
> Issue Type: Bug
> Components: Spring Integration
> Affects Versions: 9.4.1.Final
> Reporter: Jeff Skjonsby
> Assignee: Katia Aresti
> Priority: Major
>
> This test case fails:
> {code:java}
> @Test
> public void nullValuesAreNotUnwrapped() {
> Configuration config = new ConfigurationBuilder().build();
> SpringEmbeddedCacheManager cacheManager = new SpringEmbeddedCacheManager(new DefaultCacheManager(config));
> SpringCache cache = cacheManager.getCache("foo");
> cache.put("nullable", null);
> assertNull(cache.get("nullable", () -> "a"));
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-9698) SpringCache doesn't unwrap null values in get(key, valueLoader) overload
by Jeff Skjonsby (Jira)
Jeff Skjonsby created ISPN-9698:
-----------------------------------
Summary: SpringCache doesn't unwrap null values in get(key, valueLoader) overload
Key: ISPN-9698
URL: https://issues.jboss.org/browse/ISPN-9698
Project: Infinispan
Issue Type: Bug
Components: Spring Integration
Affects Versions: 9.4.1.Final
Reporter: Jeff Skjonsby
This test case fails:
{code:java}
@Test
public void nullValuesAreNotUnwrapped() {
Configuration config = new ConfigurationBuilder().build();
SpringEmbeddedCacheManager cacheManager = new SpringEmbeddedCacheManager(new DefaultCacheManager(config));
SpringCache cache = cacheManager.getCache("foo");
cache.put("nullable", null);
assertNull(cache.get("nullable", () -> "a"));
}
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-6728) Add ability to override BooleanQuery.maxClauseCount
by Adrian Nistor (Jira)
[ https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6728:
--------------------------------
Summary: Add ability to override BooleanQuery.maxClauseCount (was: Add ability to override maxClauseCount)
> Add ability to override BooleanQuery.maxClauseCount
> ----------------------------------------------------
>
> Key: ISPN-6728
> URL: https://issues.jboss.org/browse/ISPN-6728
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Querying, Server
> Reporter: Van Halbert
> Assignee: Adrian Nistor
> Priority: Minor
> Fix For: 10.0.0.Alpha1, 9.4.2.Final
>
>
> We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message:
> - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting
> This will occur when there are more than 1024 "IN" conditions specified on the query builder.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-9697) Ship correct licenses in distributions
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-9697:
-------------------------------------
Summary: Ship correct licenses in distributions
Key: ISPN-9697
URL: https://issues.jboss.org/browse/ISPN-9697
Project: Infinispan
Issue Type: Task
Components: Build
Affects Versions: 9.4.1.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.0.0.Alpha1, 9.4.2.Final
We need to ship the correct licenses in all distributed artifacts
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-6728) Add ability to override maxClauseCount
by Adrian Nistor (Jira)
[ https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6728:
--------------------------------
Fix Version/s: 9.4.2.Final
> Add ability to override maxClauseCount
> ---------------------------------------
>
> Key: ISPN-6728
> URL: https://issues.jboss.org/browse/ISPN-6728
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Querying, Server
> Reporter: Van Halbert
> Assignee: Adrian Nistor
> Priority: Minor
> Fix For: 10.0.0.Alpha1, 9.4.2.Final
>
>
> We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message:
> - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting
> This will occur when there are more than 1024 "IN" conditions specified on the query builder.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months