March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6362) Infinispan Query DSL parser failure with inheritance

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6362?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-6362: ----------------------------------- Assignee: Adrian Nistor > Infinispan Query DSL parser failure with inheritance > ---------------------------------------------------- > > Key: ISPN-6362 > URL: https://issues.jboss.org/browse/ISPN-6362 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > > As exemplified in the forum, the native DSL fails to build a query for a class who inherits an indexed field. An equivalent Hibernate Search query works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6362) Infinispan Query DSL parser failure with inheritance

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6362?page=com.atlassian.jira.plugin.... ] Work on ISPN-6362 started by Adrian Nistor. ------------------------------------------- > Infinispan Query DSL parser failure with inheritance > ---------------------------------------------------- > > Key: ISPN-6362 > URL: https://issues.jboss.org/browse/ISPN-6362 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > > As exemplified in the forum, the native DSL fails to build a query for a class who inherits an indexed field. An equivalent Hibernate Search query works -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6334) Handle definitions of indexable classes in server config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6334?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6334: -------------------------------- Fix Version/s: 9.0.0.Alpha1 > Handle definitions of indexable classes in server config > --------------------------------------------------------- > > Key: ISPN-6334 > URL: https://issues.jboss.org/browse/ISPN-6334 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Tests for server are also missing ATM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6365) Update indexless query to use Stream

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6365?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6365: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4108 > Update indexless query to use Stream > ------------------------------------ > > Key: ISPN-6365 > URL: https://issues.jboss.org/browse/ISPN-6365 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6358) Remove filterEntries method from AdvancedCache

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6358?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6358: -------------------------------- Fix Version/s: 9.0.0.Final > Remove filterEntries method from AdvancedCache > ---------------------------------------------- > > Key: ISPN-6358 > URL: https://issues.jboss.org/browse/ISPN-6358 > Project: Infinispan > Issue Type: Task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > The filterEntries method on AdvancedCache has been replaced by new DistributedStreams. The underlying implementation actually uses distributed streams now. There is no reason to keep the API around anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6358) Remove filterEntries method from AdvancedCache

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6358?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6358: ------------------------------------- The entry interator tests are now actually testing the streams. Do we still have the same coverage after removing those tests? > Remove filterEntries method from AdvancedCache > ---------------------------------------------- > > Key: ISPN-6358 > URL: https://issues.jboss.org/browse/ISPN-6358 > Project: Infinispan > Issue Type: Task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Alpha1 > > > The filterEntries method on AdvancedCache has been replaced by new DistributedStreams. The underlying implementation actually uses distributed streams now. There is no reason to keep the API around anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6358) Remove filterEntries method from AdvancedCache

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6358?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6358: -------------------------------- Status: Open (was: New) > Remove filterEntries method from AdvancedCache > ---------------------------------------------- > > Key: ISPN-6358 > URL: https://issues.jboss.org/browse/ISPN-6358 > Project: Infinispan > Issue Type: Task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Alpha1 > > > The filterEntries method on AdvancedCache has been replaced by new DistributedStreams. The underlying implementation actually uses distributed streams now. There is no reason to keep the API around anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6350) Data race in the ShardIndexManager under topology changes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6350?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6350: ------------------------------------ Labels: affinity (was: ) > Data race in the ShardIndexManager under topology changes > --------------------------------------------------------- > > Key: ISPN-6350 > URL: https://issues.jboss.org/browse/ISPN-6350 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Labels: affinity > > The following example data race can cause unrecoverable errors during indexing: > \[node1\] cache.put(key) // key maps to segment 48, owned by node1 > \[node1\] starts shard 48 > \[node1\] acquires lock on shard 48 > \[node1\] starts writing to the index > \[node1\] notification of topology changed, lock released on shard 48 > \[node1\] lock reacquired (still writing to the index) > \[node1\] commit on shard 48 > \[node1\] shard still locked > \[node2\] cache.put(key) // Node2 now owns segment 48 > \[node2\] starts shard 48 > \[node2\] tries to acquire the lock on shard 48 > \[node2\] fail (lock still owned by node1) > The current mechanism employed by the {{ShardIndexManager}} during topology changes involves using a listener and closing the IndexWriter on all nodes upon ownership changes, so that the lock is released and can be reacquired by the new owner (1 segment maps to 1 shard). > Since writing to a shard can take some time, the listener can be triggered in the middle of an index operation and the closing of the index writer will have a very short duration because it is sudden reacquired, and not released anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6350) Data race in the ShardIndexManager under topology changes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6350?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-6350: --------------------------------------- Assignee: Gustavo Fernandes > Data race in the ShardIndexManager under topology changes > --------------------------------------------------------- > > Key: ISPN-6350 > URL: https://issues.jboss.org/browse/ISPN-6350 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The following example data race can cause unrecoverable errors during indexing: > \[node1\] cache.put(key) // key maps to segment 48, owned by node1 > \[node1\] starts shard 48 > \[node1\] acquires lock on shard 48 > \[node1\] starts writing to the index > \[node1\] notification of topology changed, lock released on shard 48 > \[node1\] lock reacquired (still writing to the index) > \[node1\] commit on shard 48 > \[node1\] shard still locked > \[node2\] cache.put(key) // Node2 now owns segment 48 > \[node2\] starts shard 48 > \[node2\] tries to acquire the lock on shard 48 > \[node2\] fail (lock still owned by node1) > The current mechanism employed by the {{ShardIndexManager}} during topology changes involves using a listener and closing the IndexWriter on all nodes upon ownership changes, so that the lock is released and can be reacquired by the new owner (1 segment maps to 1 shard). > Since writing to a shard can take some time, the listener can be triggered in the middle of an index operation and the closing of the index writer will have a very short duration because it is sudden reacquired, and not released anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6350) Data race in the ShardIndexManager under topology changes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6350?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6350: ------------------------------------ Component/s: Embedded Querying > Data race in the ShardIndexManager under topology changes > --------------------------------------------------------- > > Key: ISPN-6350 > URL: https://issues.jboss.org/browse/ISPN-6350 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The following example data race can cause unrecoverable errors during indexing: > \[node1\] cache.put(key) // key maps to segment 48, owned by node1 > \[node1\] starts shard 48 > \[node1\] acquires lock on shard 48 > \[node1\] starts writing to the index > \[node1\] notification of topology changed, lock released on shard 48 > \[node1\] lock reacquired (still writing to the index) > \[node1\] commit on shard 48 > \[node1\] shard still locked > \[node2\] cache.put(key) // Node2 now owns segment 48 > \[node2\] starts shard 48 > \[node2\] tries to acquire the lock on shard 48 > \[node2\] fail (lock still owned by node1) > The current mechanism employed by the {{ShardIndexManager}} during topology changes involves using a listener and closing the IndexWriter on all nodes upon ownership changes, so that the lock is released and can be reacquired by the new owner (1 segment maps to 1 shard). > Since writing to a shard can take some time, the listener can be triggered in the middle of an index operation and the closing of the index writer will have a very short duration because it is sudden reacquired, and not released anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016