November 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8483) Error when grouping by property that is a path

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8483?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8483: ------------------------------------ Component/s: Embedded Querying Remote Querying > Error when grouping by property that is a path > ---------------------------------------------- > > Key: ISPN-8483 > URL: https://issues.jboss.org/browse/ISPN-8483 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > > If the GROUP BY clause is done on fields of internal entities of the entity queried on, the query fails. > Example, consider a 'Character' entity/message, which has an internal 'Wiki' message, both defined in protobuf. The following query: > {code:sql} > select count(c.name), c.wiki.place_of_birth from Character c group by c.wiki.place_of_birth > {code} > results in > {noformat} > ISPN014026: The expression 'wiki.place_of_birth' must be part of an aggregate function or it > should be included in the GROUP BY clause > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8482) Projection of enum field returns number instead of constant

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8482: --------------------------------------- Summary: Projection of enum field returns number instead of constant Key: ISPN-8482 URL: https://issues.jboss.org/browse/ISPN-8482 Project: Infinispan Issue Type: Bug Components: Remote Querying Affects Versions: 9.2.0.Alpha2 Reporter: Gustavo Fernandes Assignee: Adrian Nistor Consider the query below where Gender is mapped in protobuf as an {{enum}}: {code:sql} select p.gender, count(p.name) from Person p group by p.gender {code} The returned projection is numeric rather than MALE/FEMALE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8477) Rest server does not take ignored caches into account

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8477?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8477: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5564 > Rest server does not take ignored caches into account > ----------------------------------------------------- > > Key: ISPN-8477 > URL: https://issues.jboss.org/browse/ISPN-8477 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > It's currently hardcoding the logic if a cache should be ignored or not as FALSE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8477) Rest server does not take ignored caches into account

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8477?page=com.atlassian.jira.plugin.... ] Work on ISPN-8477 started by Gustavo Fernandes. ----------------------------------------------- > Rest server does not take ignored caches into account > ----------------------------------------------------- > > Key: ISPN-8477 > URL: https://issues.jboss.org/browse/ISPN-8477 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > It's currently hardcoding the logic if a cache should be ignored or not as FALSE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8477) Rest server does not take ignored caches into account

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8477?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8477: ------------------------------------ Status: Open (was: New) > Rest server does not take ignored caches into account > ----------------------------------------------------- > > Key: ISPN-8477 > URL: https://issues.jboss.org/browse/ISPN-8477 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > It's currently hardcoding the logic if a cache should be ignored or not as FALSE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8454) Off Heap can crash when using JMH test

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8454?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8454: -------------------------------- Fix Version/s: 9.1.3.Final > Off Heap can crash when using JMH test > -------------------------------------- > > Key: ISPN-8454 > URL: https://issues.jboss.org/browse/ISPN-8454 > Project: Infinispan > Issue Type: Bug > Components: Off Heap > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1, 9.1.3.Final > > > I have a jmh branch from our benchmarks that always can crash off heap when not using tracing. For whatever reason I can't seem to reliably produce it with tracing. This JIRA is to handle this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8481) Lazily calculate hashCode for WrappedByteArray

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8481?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8481: -------------------------------- Status: Open (was: New) > Lazily calculate hashCode for WrappedByteArray > ---------------------------------------------- > > Key: ISPN-8481 > URL: https://issues.jboss.org/browse/ISPN-8481 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1 > > > We don't always use the hashCode for a WrappedByteArray. By always calculating it this adds additional cost, we should see if we can change this safely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8481) Lazily calculate hashCode for WrappedByteArray

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8481?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8481: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5563 > Lazily calculate hashCode for WrappedByteArray > ---------------------------------------------- > > Key: ISPN-8481 > URL: https://issues.jboss.org/browse/ISPN-8481 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1 > > > We don't always use the hashCode for a WrappedByteArray. By always calculating it this adds additional cost, we should see if we can change this safely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8481) Lazily calculate hashCode for WrappedByteArray

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8481?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8481: -------------------------------- Fix Version/s: 9.2.0.Beta1 > Lazily calculate hashCode for WrappedByteArray > ---------------------------------------------- > > Key: ISPN-8481 > URL: https://issues.jboss.org/browse/ISPN-8481 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1 > > > We don't always use the hashCode for a WrappedByteArray. By always calculating it this adds additional cost, we should see if we can change this safely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8481) Lazily calculate hashCode for WrappedByteArray

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8481?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8481: ------------------------------------- Here is the JMH run from this https://gist.github.com/wburns/3744e3b2210466102378948cbb2105f0 It isn't much better if at all really compared to https://issues.jboss.org/browse/ISPN-8454?focusedCommentId=13485334&page=... but it should help when the entries are larger. The largest value here was only 1000 bytes > Lazily calculate hashCode for WrappedByteArray > ---------------------------------------------- > > Key: ISPN-8481 > URL: https://issues.jboss.org/browse/ISPN-8481 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > > We don't always use the hashCode for a WrappedByteArray. By always calculating it this adds additional cost, we should see if we can change this safely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2017