April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4593) Expose a method to remove all instances of a type from the indexes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4593?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4593: ----------------------------------------------- Gustavo Fernandes <gfernand(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from ASSIGNED to MODIFIED > Expose a method to remove all instances of a type from the indexes > ------------------------------------------------------------------ > > Key: ISPN-4593 > URL: https://issues.jboss.org/browse/ISPN-4593 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > In Hibernate Search we have a method "purgeAll( type )", it seems Infinispan Query is missing this operation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5034) Non blocking MassIndexer execution

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5034?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5034: ----------------------------------------------- Gustavo Fernandes <gfernand(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from ASSIGNED to MODIFIED > Non blocking MassIndexer execution > ---------------------------------- > > Key: ISPN-5034 > URL: https://issues.jboss.org/browse/ISPN-5034 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.1.0.Final > > > Currently the MassIndexer can only be run in a blocking way by calling {{MassIndexer.start()}} > Alternatively, it should be able to return a Future<?> that be can cancelled or waited for a custom period of time -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5368) Out of order events produced when using the MassIndexer with async backend

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5368?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5368: ----------------------------------------------- Gustavo Fernandes <gfernand(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from ASSIGNED to MODIFIED > Out of order events produced when using the MassIndexer with async backend > -------------------------------------------------------------------------- > > Key: ISPN-5368 > URL: https://issues.jboss.org/browse/ISPN-5368 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.2.0.Beta2, 7.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.2.0.CR1, 7.2.0.Final > > > When using async indexing backend on DIST caches with shared index (InfinispanIndexManager), the MassIndexer fails to re-index all the entries, if it is run from a node that is not > the indexing master. > Normally the operation sequence of the MassIndexer in the above configuration, for a two node cluster is: > * Purge the index > * Send index job to node A and to node B > * Flush > Given the backend is async, all index commands are sent to the master RPC-wise asynchronously, and so a reorder can occur and produce like: > * Send index job to node A > * Purge > * Send index job to node B > * Flush > Causing previously re-indexed entries to be wiped -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4644) MassIndexer causes unecessary commits to the index when used with InfinispanIndexManager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4644?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4644: ----------------------------------------------- Gustavo Fernandes <gfernand(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from ASSIGNED to MODIFIED > MassIndexer causes unecessary commits to the index when used with InfinispanIndexManager > ---------------------------------------------------------------------------------------- > > Key: ISPN-4644 > URL: https://issues.jboss.org/browse/ISPN-4644 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5347) Extend org.infinispan.objectfilter.Matcher to support event types and user context data

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5347?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5347: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3393 (was: https://github.com/infinispan/infinispan/pull/3351) > Extend org.infinispan.objectfilter.Matcher to support event types and user context data > --------------------------------------------------------------------------------------- > > Key: ISPN-5347 > URL: https://issues.jboss.org/browse/ISPN-5347 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > The Matcher should accept a user context object and an event type object beside the instance being tested and should pass the user context and event type to the callback of the matching subscriptions. The user context object and event type should be optional. > Also, when subscribing the user should be able to specify an optional event type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5388?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5388: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3393 > Optimize redundant predicates (non-indexed query) > ------------------------------------------------- > > Key: ISPN-5388 > URL: https://issues.jboss.org/browse/ISPN-5388 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: > * X || X => X > * X && X => X > * !X || !X => !X > * !X && !X => !X > * X || !X => TRUE (tautology) > * X && !X => FALSE (contradiction) > (where X is a predicate not a general boolean expression) > Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5388?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5388: -------------------------------- Status: Open (was: New) > Optimize redundant predicates (non-indexed query) > ------------------------------------------------- > > Key: ISPN-5388 > URL: https://issues.jboss.org/browse/ISPN-5388 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: > * X || X => X > * X && X => X > * !X || !X => !X > * !X && !X => !X > * X || !X => TRUE (tautology) > * X && !X => FALSE (contradiction) > (where X is a predicate not a general boolean expression) > Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5388?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5388: -------------------------------- Description: Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: * X || X => X * X && X => X * !X || !X => !X * !X && !X => !X * X || !X => TRUE (tautology) * X && !X => FALSE (contradiction) (where X is a predicate not a general boolean expression) Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. was: Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: * X || X => X * X && X => X * !X || !X => !X * !X && !X => !X * X || !X => TRUE * X && !X => FALSE (where X is a predicate not a general boolean expression) Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. > Optimize redundant predicates (non-indexed query) > ------------------------------------------------- > > Key: ISPN-5388 > URL: https://issues.jboss.org/browse/ISPN-5388 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: > * X || X => X > * X && X => X > * !X || !X => !X > * !X && !X => !X > * X || !X => TRUE (tautology) > * X && !X => FALSE (contradiction) > (where X is a predicate not a general boolean expression) > Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5388: ----------------------------------- Summary: Optimize redundant predicates (non-indexed query) Key: ISPN-5388 URL: https://issues.jboss.org/browse/ISPN-5388 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying Affects Versions: 7.0.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.2.0.CR1, 7.2.0.Final Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: * X || X => X * X && X => X * !X || !X => !X * !X && !X => !X * X || !X => TRUE * X && !X => FALSE (where X is a predicate not a general boolean expression) Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5264) Optimize PutAll operations (library mode)

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5264?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5264: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3354, https://github.com/infinispan/infinispan/pull/3364, https://github.com/infinispan/infinispan/pull/3367, https://github.com/infinispan/infinispan/pull/3392 (was: https://github.com/infinispan/infinispan/pull/3354, https://github.com/infinispan/infinispan/pull/3364, https://github.com/infinispan/infinispan/pull/3367) > Optimize PutAll operations (library mode) > ----------------------------------------- > > Key: ISPN-5264 > URL: https://issues.jboss.org/browse/ISPN-5264 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > Fix For: 7.2.0.CR1, 7.2.0.Final > > > - PutAll: to ensure that users can load massive amount of data into the grid quickly in Library mode > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 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 April 2015