November 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5923) Wrong results when applying the <= operator to a string attribute having a null token defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5923?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5923: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1254053|https://bugzilla.redhat.com/show_bug.cgi?id=1254053] from MODIFIED to POST > Wrong results when applying the <= operator to a string attribute having a null token defined > --------------------------------------------------------------------------------------------- > > Key: ISPN-5923 > URL: https://issues.jboss.org/browse/ISPN-5923 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.1.Final, 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.0.2.Final > > > The query having("myField").lte("Something") gets translated to lucene as myField:['_null_' TO 'Something'] where _null_ is the defined null token for this field. This query returns wrong results or no results at all, depending on the value of the null token. The issue no longer appears if there is no null token defined; it will get properly translated to myField:[* TO 'Something'] . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5880) XSite client failover - enhance configuration validation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5880?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5880: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1273796|https://bugzilla.redhat.com/show_bug.cgi?id=1273796] from ON_QA to VERIFIED > XSite client failover - enhance configuration validation > -------------------------------------------------------- > > Key: ISPN-5880 > URL: https://issues.jboss.org/browse/ISPN-5880 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication, Remote Protocols > Reporter: Matej Čimbora > Assignee: Matej Čimbora > Fix For: 8.1.0.Beta1 > > > Improve validation of cluster configuration for HR client to handle scenarios such as specifying duplicate backup clusters and omitting node list for a defined cluster. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5882) XSite replication - take-offline.after-failures property is ignored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5882?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5882: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1274800|https://bugzilla.redhat.com/show_bug.cgi?id=1274800] from ON_QA to VERIFIED > XSite replication - take-offline.after-failures property is ignored > ------------------------------------------------------------------- > > Key: ISPN-5882 > URL: https://issues.jboss.org/browse/ISPN-5882 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Reporter: Matej Čimbora > Assignee: Pedro Ruivo > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Let's say I use the following backup settings and start the server in site LON: > <backup site="BRN" strategy="SYNC"> > <take-offline after-failures="5"/> > </backup> > The following code snipped should cause BRN site to go offline after 5 failures, however the site is still remains online and tries to back up the data to BRN. > RemoteCacheManager remoteCacheManager = new RemoteCacheManager(); > RemoteCache<Object, Object> cache = remoteCacheManager.getCache(); > for (int i = 0; i < 10; i++) { > cache.put(i, i); > } > Server-side error message example: > 16:05:19,121 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerWorker-5-2) localhost: no route to BRN: dropping message > 16:05:29,121 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerWorker-5-2) ISPN000202: Problems backing up data for cache default to site BRN: org.infinispan.util.concurrent.TimeoutException: Timed out after 10 seconds waiting for a response from BRN (sync, timeout=10000) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5802) Deprecate DataContainer API as no longer pluggable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5802?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5802: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3804 > Deprecate DataContainer API as no longer pluggable > -------------------------------------------------- > > Key: ISPN-5802 > URL: https://issues.jboss.org/browse/ISPN-5802 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: William Burns > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > We'll keep the current {{DataContainer}} implementations but we need to deprecate its public API to allow more flexible evolution in the near future. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5802) Deprecate DataContainer API as no longer pluggable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5802?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5802: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Final Resolution: Done > Deprecate DataContainer API as no longer pluggable > -------------------------------------------------- > > Key: ISPN-5802 > URL: https://issues.jboss.org/browse/ISPN-5802 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: William Burns > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > We'll keep the current {{DataContainer}} implementations but we need to deprecate its public API to allow more flexible evolution in the near future. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5613) Replication timeouts should show more information of the affected entries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5613?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5613: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Beta1 8.1.0.Final 8.0.2.Final Resolution: Done > Replication timeouts should show more information of the affected entries > ------------------------------------------------------------------------- > > Key: ISPN-5613 > URL: https://issues.jboss.org/browse/ISPN-5613 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Fix For: 8.1.0.Beta1, 8.1.0.Final, 8.0.2.Final > > > Typical timeouts for replication are > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (remote-thread-595) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Replication timeout for jboss####-##### > and > ERROR .... > Caused by: org.infinispan.util.concurrent.TimeoutException: Node jboss####-##### timed out > The issue is that it is not possible to check what key/entry is affected. > The cache can become inconsistent between nodes. > There should be an information which key is affected. > For some operations it is not possible at all as there is no information about the entries (i.e. commit) or the key is binary or custom without a valid toString() method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5905) Avoid creating a FilterEvalContext for non-matching subscriptions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5905?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5905: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Final Resolution: Done > Avoid creating a FilterEvalContext for non-matching subscriptions > ----------------------------------------------------------------- > > Key: ISPN-5905 > URL: https://issues.jboss.org/browse/ISPN-5905 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.1.0.Final, 8.0.2.Final > > > MatcherEvalContext.getFilterEvalContext crates a FilterEvalContext on the fly. > So during the dispatching of notifications all FilterEvalContexts get created, even for non-matching subscriptions. This can be easily avoided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5906) Hide implementation details from package org.infinispan.query.continuous

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5906?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5906: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Final Resolution: Done > Hide implementation details from package org.infinispan.query.continuous > ------------------------------------------------------------------------ > > Key: ISPN-5906 > URL: https://issues.jboss.org/browse/ISPN-5906 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.1.0.Final, 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5923) Wrong results when applying the <= operator to a string attribute having a null token defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5923?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5923: ----------------------------------------------- Sanne Grinovero <sanne(a)redhat.com> changed the Status of [bug 1254053|https://bugzilla.redhat.com/show_bug.cgi?id=1254053] from ASSIGNED to MODIFIED > Wrong results when applying the <= operator to a string attribute having a null token defined > --------------------------------------------------------------------------------------------- > > Key: ISPN-5923 > URL: https://issues.jboss.org/browse/ISPN-5923 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.1.Final, 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.0.2.Final > > > The query having("myField").lte("Something") gets translated to lucene as myField:['_null_' TO 'Something'] where _null_ is the defined null token for this field. This query returns wrong results or no results at all, depending on the value of the null token. The issue no longer appears if there is no null token defined; it will get properly translated to myField:[* TO 'Something'] . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5819) Add global backup site ops to container

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5819?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5819: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Beta1 8.1.0.Final Resolution: Done > Add global backup site ops to container > --------------------------------------- > > Key: ISPN-5819 > URL: https://issues.jboss.org/browse/ISPN-5819 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication, Server > Reporter: Tristan Tarrant > Assignee: Pedro Ruivo > Labels: jdg7 > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Add corresponding global remote backup ops to container so that they can be applied to all caches backed-up to a specific site. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2015