[JBoss JIRA] (ISPN-5791) Query DSL : Projecting a Date field multiple times will render it as string
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5791?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-5791:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1277075
Bugzilla Update: Perform
> Query DSL : Projecting a Date field multiple times will render it as string
> ---------------------------------------------------------------------------
>
> Key: ISPN-5791
> URL: https://issues.jboss.org/browse/ISPN-5791
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta1, 8.0.2.Final
>
>
> Adding this in QueryDslConditionsTest fails. The second date projection is a String instead of being a Date. First projection is OK. The problem is gone if cache is not indexed, which makes me think it is more of a problem in CacheQuery.
> {code}
> public void testDuplicateDateProjection() throws Exception {
> QueryFactory qf = getQueryFactory();
> Query q = qf.from(getModelFactory().getTransactionImplClass())
> .select("id", "date", "date")
> .having("description").eq("Hotel")
> .toBuilder().build();
> List<Object[]> list = q.list();
> assertEquals(1, list.size());
> assertEquals(1, list.size());
> assertEquals(3, list.get(0).length);
> assertEquals(3, list.get(0)[0]);
> assertEquals(makeDate("2013-02-27"), list.get(0)[1]);
> assertEquals(makeDate("2013-02-27"), list.get(0)[2]);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (ISPN-5903) Spring package split
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created ISPN-5903:
-----------------------------------------
Summary: Spring package split
Key: ISPN-5903
URL: https://issues.jboss.org/browse/ISPN-5903
Project: Infinispan
Issue Type: Enhancement
Reporter: Sebastian Łaskawiec
Assignee: Sebastian Łaskawiec
Into:
* remote
* embedded
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (ISPN-5896) ClusterStreamManager segment generation should use locatePrimaryOwnerForSegment
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5896?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5896:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> ClusterStreamManager segment generation should use locatePrimaryOwnerForSegment
> -------------------------------------------------------------------------------
>
> Key: ISPN-5896
> URL: https://issues.jboss.org/browse/ISPN-5896
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 8.1.0.Alpha2
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 8.1.0.Beta1, 8.0.2.Final
>
>
> ClusterStreamManager has to find all of the addresses for a given set of segments. Unfortunately it does this by finding the segments per address. This ends up having n * m time complexity. If we instead did it so we find the primary owner per segment it would only have n time complexity as finding the primary owner of a segment is constant time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months