September 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5732) Aggregation functions should ignore NULL values

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5732?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5732: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3698 > Aggregation functions should ignore NULL values > ----------------------------------------------- > > Key: ISPN-5732 > URL: https://issues.jboss.org/browse/ISPN-5732 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Jakub Markos > Assignee: Adrian Nistor > Fix For: 8.0.1.Final > > > For example, this query returns 3 (in QueryDslConditionsTest) > {code} > public void testCountNull() { > QueryFactory qf = getQueryFactory(); > Query q = qf.from(getModelFactory().getUserImplClass()) > .select(Expression.count("age")) > .build(); > {code} > while only 1 value is non-null. > It might be good to behave like JPA, which ignores NULL values: > "Null values are eliminated before the aggregate function is applied, regardless of whether the keyword DISTINCT is specified." http://download.oracle.com/otn-pub/jcp/persistence-2.0-fr-eval-oth-JSpec/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5732) Aggregation functions should ignore NULL values

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5732?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5732: -------------------------------- Fix Version/s: 8.0.1.Final > Aggregation functions should ignore NULL values > ----------------------------------------------- > > Key: ISPN-5732 > URL: https://issues.jboss.org/browse/ISPN-5732 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Jakub Markos > Assignee: Adrian Nistor > Fix For: 8.0.1.Final > > > For example, this query returns 3 (in QueryDslConditionsTest) > {code} > public void testCountNull() { > QueryFactory qf = getQueryFactory(); > Query q = qf.from(getModelFactory().getUserImplClass()) > .select(Expression.count("age")) > .build(); > {code} > while only 1 value is non-null. > It might be good to behave like JPA, which ignores NULL values: > "Null values are eliminated before the aggregate function is applied, regardless of whether the keyword DISTINCT is specified." http://download.oracle.com/otn-pub/jcp/persistence-2.0-fr-eval-oth-JSpec/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5732) Aggregation functions should ignore NULL values

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5732?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5732: -------------------------------- Affects Version/s: 8.0.0.Final > Aggregation functions should ignore NULL values > ----------------------------------------------- > > Key: ISPN-5732 > URL: https://issues.jboss.org/browse/ISPN-5732 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Jakub Markos > Assignee: Adrian Nistor > Fix For: 8.0.1.Final > > > For example, this query returns 3 (in QueryDslConditionsTest) > {code} > public void testCountNull() { > QueryFactory qf = getQueryFactory(); > Query q = qf.from(getModelFactory().getUserImplClass()) > .select(Expression.count("age")) > .build(); > {code} > while only 1 value is non-null. > It might be good to behave like JPA, which ignores NULL values: > "Null values are eliminated before the aggregate function is applied, regardless of whether the keyword DISTINCT is specified." http://download.oracle.com/otn-pub/jcp/persistence-2.0-fr-eval-oth-JSpec/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5713) Extend Continuous Query test coverage

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5713?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5713: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.0.1.Final Resolution: Done Integrated in master. Thanks [~vjuranek]! > Extend Continuous Query test coverage > ------------------------------------- > > Key: ISPN-5713 > URL: https://issues.jboss.org/browse/ISPN-5713 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 8.0.1.Final > > > Implement test which > * verifies that notification is sent also for expired entries > * updates work correctly also for more complex queries which combines several predicates > * updates work correctly when node a started/shut down -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5717) Continuous query ignores expired entries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5717?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5717: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1258982|https://bugzilla.redhat.com/show_bug.cgi?id=1258982] from POST to MODIFIED > Continuous query ignores expired entries > ---------------------------------------- > > Key: ISPN-5717 > URL: https://issues.jboss.org/browse/ISPN-5717 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 8.0.1.Final > > > When cache entry expires, CQ listeners are not updated and thus can server obsolete results -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5713) Extend Continuous Query test coverage

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5713?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5713: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1258982|https://bugzilla.redhat.com/show_bug.cgi?id=1258982] from POST to MODIFIED > Extend Continuous Query test coverage > ------------------------------------- > > Key: ISPN-5713 > URL: https://issues.jboss.org/browse/ISPN-5713 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Implement test which > * verifies that notification is sent also for expired entries > * updates work correctly also for more complex queries which combines several predicates > * updates work correctly when node a started/shut down -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5704) Enhancements for Functional Map API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5704?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5704: ---------------------------------------- Shall we provide order guarantees for Traversable returned from multi-key (evalMany methods) operations? Right now it's not guaranteed but it's implied. > Enhancements for Functional Map API > ----------------------------------- > > Key: ISPN-5704 > URL: https://issues.jboss.org/browse/ISPN-5704 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final > > > List of enhancements that didn't make it into 8.0: > * Transaction support. > * Verify locks are acquired for all operations (once tx is in place, locks can be checked easily) > * Complete persistence support (remove many returning previous, put many returning previous, remove many) > * Replication of per-invocation parameters. > * Port mode *Becoming*Test to functional APIs, and expand on testing other functional APIs. > * Test interoperability with cache, e.g. cache put with lifespan can be retrieved via functional map with lifespan, and viceversa > * Test compatibility mode > * Add more listener events: activation, passivation and expiration. > * Use check isLocal instead of `e == null` in command impls > * Fix branch skip issue (see previous PR: https://github.com/infinispan/infinispan/pull/3571) > * Add externalizers for primitive versions of Optional. > * ValueMatcherMode indexes in MarshallableFunctionExternalizers should be based on {{ordinal()}} calls to annotation. Also, could the core's enumeration use the annotations defined in commons? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5704) Enhancements for Functional Map API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5704?page=com.atlassian.jira.plugin.... ] Galder Zamarreño edited comment on ISPN-5704 at 9/8/15 5:09 AM: ---------------------------------------------------------------- evalMany methods taking Map should be typed more generically because the way {{entries}} has been defined, it can only carry value information but no metadata paramaters. In other words, with {{entries}} value side being {{? extends V}}, it's difficult to construct to a Map where you have both value and metadata information, and then apply that. Here's how it looks now in WriteOnlyMap: {code} CompletableFuture<Void> evalMany(Map<? extends K, ? extends V> entries, BiConsumer<V, WriteEntryView<V>> f); {code} Here's how it could look: {code} <T> CompletableFuture<Void> evalMany(Map<? extends K, T> entries, BiConsumer<T, WriteEntryView<V>> f); {code} By doing that, T could be flexible enough to contain both value and any extra metadata parameters. was (Author: galder.zamarreno): * evalMany methods taking Map should be typed more generically because the way {{entries}} has been defined, it can only carry value information but no metadata paramaters. In other words, with {{entries}} value side being {{? extends V}}, it's difficult to construct to a Map where you have both value and metadata information, and then apply that. Here's how it looks now in WriteOnlyMap: {code} CompletableFuture<Void> evalMany(Map<? extends K, ? extends V> entries, BiConsumer<V, WriteEntryView<V>> f); {code} Here's how it could look: {code} <T> CompletableFuture<Void> evalMany(Map<? extends K, T> entries, BiConsumer<T, WriteEntryView<V>> f); {code} By doing that, T could be flexible enough to contain both value and any extra metadata parameters. > Enhancements for Functional Map API > ----------------------------------- > > Key: ISPN-5704 > URL: https://issues.jboss.org/browse/ISPN-5704 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final > > > List of enhancements that didn't make it into 8.0: > * Transaction support. > * Verify locks are acquired for all operations (once tx is in place, locks can be checked easily) > * Complete persistence support (remove many returning previous, put many returning previous, remove many) > * Replication of per-invocation parameters. > * Port mode *Becoming*Test to functional APIs, and expand on testing other functional APIs. > * Test interoperability with cache, e.g. cache put with lifespan can be retrieved via functional map with lifespan, and viceversa > * Test compatibility mode > * Add more listener events: activation, passivation and expiration. > * Use check isLocal instead of `e == null` in command impls > * Fix branch skip issue (see previous PR: https://github.com/infinispan/infinispan/pull/3571) > * Add externalizers for primitive versions of Optional. > * ValueMatcherMode indexes in MarshallableFunctionExternalizers should be based on {{ordinal()}} calls to annotation. Also, could the core's enumeration use the annotations defined in commons? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5704) Enhancements for Functional Map API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5704?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5704: ---------------------------------------- * evalMany methods taking Map should be typed more generically because the way {{entries}} has been defined, it can only carry value information but no metadata paramaters. In other words, with {{entries}} value side being {{? extends V}}, it's difficult to construct to a Map where you have both value and metadata information, and then apply that. Here's how it looks now in WriteOnlyMap: {code} CompletableFuture<Void> evalMany(Map<? extends K, ? extends V> entries, BiConsumer<V, WriteEntryView<V>> f); {code} Here's how it could look: {code} <T> CompletableFuture<Void> evalMany(Map<? extends K, T> entries, BiConsumer<T, WriteEntryView<V>> f); {code} By doing that, T could be flexible enough to contain both value and any extra metadata parameters. > Enhancements for Functional Map API > ----------------------------------- > > Key: ISPN-5704 > URL: https://issues.jboss.org/browse/ISPN-5704 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final > > > List of enhancements that didn't make it into 8.0: > * Transaction support. > * Verify locks are acquired for all operations (once tx is in place, locks can be checked easily) > * Complete persistence support (remove many returning previous, put many returning previous, remove many) > * Replication of per-invocation parameters. > * Port mode *Becoming*Test to functional APIs, and expand on testing other functional APIs. > * Test interoperability with cache, e.g. cache put with lifespan can be retrieved via functional map with lifespan, and viceversa > * Test compatibility mode > * Add more listener events: activation, passivation and expiration. > * Use check isLocal instead of `e == null` in command impls > * Fix branch skip issue (see previous PR: https://github.com/infinispan/infinispan/pull/3571) > * Add externalizers for primitive versions of Optional. > * ValueMatcherMode indexes in MarshallableFunctionExternalizers should be based on {{ordinal()}} calls to annotation. Also, could the core's enumeration use the annotations defined in commons? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5520) Add XSite failover for HotRod clients

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5520?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5520: ---------------------------------------- Design wiki: https://github.com/infinispan/infinispan/wiki/XSite-Failover-for-Hot-Rod-... > Add XSite failover for HotRod clients > ------------------------------------- > > Key: ISPN-5520 > URL: https://issues.jboss.org/browse/ISPN-5520 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication, Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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