[JBoss JIRA] (ISPN-6012) Too many warnings about unsolicited state during cluster shutdown
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6012?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6012:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Integrated in master. Thanks [~dan.berindei]!
> Too many warnings about unsolicited state during cluster shutdown
> -----------------------------------------------------------------
>
> Key: ISPN-6012
> URL: https://issues.jboss.org/browse/ISPN-6012
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.0.2.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.1.0.Final
>
>
> When shutting down, {{StateConsumerImpl}} first clears the map of inbound transfers. Any {{StateResponseCommand}} received afterwards will trigger a {{Received unsolicited state from node %s for segment %d of cache %s}} warning. We should just ignore any {{StateResponseCommand}} received during shutdown, without any warning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-6008) Query DSL groupBy and orderBy should only accept single-valued properties
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6008?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6008:
--------------------------------
Description:
{code}
QueryFactory qf = getQueryFactory();
Query q = qf.from(User.class)
.select(Expression.min("name"))
.groupBy("addresses.street")
.build();
q.list();
{code}
Should throw an exception during query parsing because property "addresses.street" is not single-valued.
Similar behaviour should be expected for orderBy.
was:
{code}
QueryFactory qf = getQueryFactory();
Query q = qf.from(getModelFactory().getUserImplClass())
.select(Expression.min("name"))
.groupBy("addresses.street")
.build();
q.list();
{code}
Should throw an exception during query parsing because property "addresses.street" is not single-valued.
Similar behaviour should be expected for orderBy.
> Query DSL groupBy and orderBy should only accept single-valued properties
> -------------------------------------------------------------------------
>
> Key: ISPN-6008
> URL: https://issues.jboss.org/browse/ISPN-6008
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 8.1.0.CR1, 8.0.2.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Final, 8.0.3.Final
>
>
> {code}
> QueryFactory qf = getQueryFactory();
> Query q = qf.from(User.class)
> .select(Expression.min("name"))
> .groupBy("addresses.street")
> .build();
> q.list();
> {code}
> Should throw an exception during query parsing because property "addresses.street" is not single-valued.
> Similar behaviour should be expected for orderBy.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-6008) Query DSL groupBy and orderBy should only accept single-valued properties
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6008?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6008:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Query DSL groupBy and orderBy should only accept single-valued properties
> -------------------------------------------------------------------------
>
> Key: ISPN-6008
> URL: https://issues.jboss.org/browse/ISPN-6008
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 8.1.0.CR1, 8.0.2.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Final, 8.0.3.Final
>
>
> {code}
> QueryFactory qf = getQueryFactory();
> Query q = qf.from(getModelFactory().getUserImplClass())
> .select(Expression.min("name"))
> .groupBy("addresses.street")
> .build();
> q.list();
> {code}
> Should throw an exception during query parsing because property "addresses.street" is not single-valued.
> Similar behaviour should be expected for orderBy.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-6008) Query DSL groupBy and orderBy should only accept single-valued properties
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6008?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-6008:
-------------------------------------
I initially thought groupBy on multivalued properties does not make sense but it seems there are valid uses for it. For now we'll disallow it because it does not work properly and cannot be fixed in the 8.1.x timeframe. The problem will be readdressed in ISPN-6015 on 8.2.x.
As for orderBy, this will be disabled for good.
> Query DSL groupBy and orderBy should only accept single-valued properties
> -------------------------------------------------------------------------
>
> Key: ISPN-6008
> URL: https://issues.jboss.org/browse/ISPN-6008
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 8.1.0.CR1, 8.0.2.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Final, 8.0.3.Final
>
>
> {code}
> QueryFactory qf = getQueryFactory();
> Query q = qf.from(getModelFactory().getUserImplClass())
> .select(Expression.min("name"))
> .groupBy("addresses.street")
> .build();
> q.list();
> {code}
> Should throw an exception during query parsing because property "addresses.street" is not single-valued.
> Similar behaviour should be expected for orderBy.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-6015) Query DSL should support groupBy for multi-valued properties
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-6015:
-----------------------------------
Summary: Query DSL should support groupBy for multi-valued properties
Key: ISPN-6015
URL: https://issues.jboss.org/browse/ISPN-6015
Project: Infinispan
Issue Type: Feature Request
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 8.2.0.Alpha1, 8.2.0.Final
If a groupBy property is multivalued the entity will belong to multiple groups, one for each distinct value.
Current implementation in 8.0.x and 8.1.x does not allow this and instead of providing invalid results grouping by multivalued property was disallowed (see ISPN-6008).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months