February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-5465) Replace the Hash function with a segment mapper

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5465?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5465: ------------------------------------ I changed the interface name to {{KeyPartitioner}}. > Replace the Hash function with a segment mapper > ----------------------------------------------- > > Key: ISPN-5465 > URL: https://issues.jboss.org/browse/ISPN-5465 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1 > > > Currently, we allow the user to customize the mapping of keys to CH segments with a custom {{Hash}} function. But the Hash function doesn't give the user direct control over where a key is mapped, the ultimate location depends on the CH implementation. The CH implementation is also customizable, but it's much harder for the user to get right. > We should replace the Hash with something like this: > {code:java} > public interface SegmentMapper { > public int getSegment(Object key, int numSegments); > {code} > This should also be easier to implement than the {{Grouper}} interface we have now, when the user only needs co-location and doesn't need additional grouping features like {{cache.getGroup(name)}}. > I think this should also help internally, e.g. to replace the {{GroupingConsistentHash}} that needs to be re-created on every topology update with a constant {{SegmentMapper}} wrapper. It might also help to compute the segment of a key only once and save it in the context, instead of computing it every time we need to know the location of a key. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5414) Support (named) parameters in DSL based queries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5414?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5414: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3629, https://github.com/infinispan/infinispan/pull/3963, https://github.com/infinispan/infinispan/pull/3972 (was: https://github.com/infinispan/infinispan/pull/3629, https://github.com/infinispan/infinispan/pull/3963) > Support (named) parameters in DSL based queries > ----------------------------------------------- > > Key: ISPN-5414 > URL: https://issues.jboss.org/browse/ISPN-5414 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6121) query-dsl server module must list jboss-logging dependency

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6121?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6121: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3963, https://github.com/infinispan/infinispan/pull/3972 (was: https://github.com/infinispan/infinispan/pull/3963) > query-dsl server module must list jboss-logging dependency > ---------------------------------------------------------- > > Key: ISPN-6121 > URL: https://issues.jboss.org/browse/ISPN-6121 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6119) Query DSL should not accept null or empty parameter name

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6119?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6119: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3963, https://github.com/infinispan/infinispan/pull/3972 (was: https://github.com/infinispan/infinispan/pull/3963) > Query DSL should not accept null or empty parameter name > -------------------------------------------------------- > > Key: ISPN-6119 > URL: https://issues.jboss.org/browse/ISPN-6119 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.2.0.Final, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6119) Query DSL should not accept null or empty parameter name

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6119?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6119: -------------------------------- Fix Version/s: 8.1.2.Final > Query DSL should not accept null or empty parameter name > -------------------------------------------------------- > > Key: ISPN-6119 > URL: https://issues.jboss.org/browse/ISPN-6119 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.2.0.Final, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6121) query-dsl server module must list jboss-logging dependency

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6121?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6121: -------------------------------- Fix Version/s: 8.1.2.Final > query-dsl server module must list jboss-logging dependency > ---------------------------------------------------------- > > Key: ISPN-6121 > URL: https://issues.jboss.org/browse/ISPN-6121 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6106) FilterConditionEndContext.between(from, to) should check args are Comparable

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6106?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6106: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3959, https://github.com/infinispan/infinispan/pull/3972 (was: https://github.com/infinispan/infinispan/pull/3959) > FilterConditionEndContext.between(from, to) should check args are Comparable > ---------------------------------------------------------------------------- > > Key: ISPN-6106 > URL: https://issues.jboss.org/browse/ISPN-6106 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.2.0.Final, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6106) FilterConditionEndContext.between(from, to) should check args are Comparable

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6106?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6106: -------------------------------- Fix Version/s: 8.1.2.Final > FilterConditionEndContext.between(from, to) should check args are Comparable > ---------------------------------------------------------------------------- > > Key: ISPN-6106 > URL: https://issues.jboss.org/browse/ISPN-6106 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.2.0.Final, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6130) # Activations in management console is allways 0

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6130?page=com.atlassian.jira.plugin.... ] Martin Vrabel updated ISPN-6130: -------------------------------- Description: Page: Caches -> select cache container -> select cache. Configuration of the cache: replicated cache, 2 nodes in the domain In the Entries lifecycle" tab, there is a field "# Activations" which should show number of Activations . When I put 30 entries in the cache and read 30, this field should show 30. was: Page: Caches -> select cache container -> select cache. Configuration of the cache: replicated cache, 2 nodes in the domain In the Entries lifecycle" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. > # Activations in management console is allways 0 > -------------------------------------------------- > > Key: ISPN-6130 > URL: https://issues.jboss.org/browse/ISPN-6130 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Martin Vrabel > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the Entries lifecycle" tab, there is a field "# Activations" which should show number of Activations . When I put 30 entries in the cache and read 30, this field should show 30. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6130) # Activations in management console is allways 0

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6130?page=com.atlassian.jira.plugin.... ] Martin Vrabel updated ISPN-6130: -------------------------------- Description: Page: Caches -> select cache container -> select cache. Configuration of the cache: replicated cache, 2 nodes in the domain In the Entries lifecycle" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. > # Activations in management console is allways 0 > -------------------------------------------------- > > Key: ISPN-6130 > URL: https://issues.jboss.org/browse/ISPN-6130 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Martin Vrabel > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the Entries lifecycle" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016