June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7739) CacheMgmtInterceptor should collect total writes stat

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7739?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7739: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > CacheMgmtInterceptor should collect total writes stat > ----------------------------------------------------- > > Key: ISPN-7739 > URL: https://issues.jboss.org/browse/ISPN-7739 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7729) Cache managers share a mutable GenericTransactionManagerLookup instance

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7729?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7729: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Cache managers share a mutable GenericTransactionManagerLookup instance > ----------------------------------------------------------------------- > > Key: ISPN-7729 > URL: https://issues.jboss.org/browse/ISPN-7729 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 9.0.0.Final > Reporter: Dan Berindei > Fix For: 9.4.0.Final > > > {{GenericTransactionManagerLookup}} is mutable, so different cache managers should use different instances. Even if two deployments see the same {{GenericTransactionManagerLookup}} class from a common parent classloader, each deployment could include its own transaction manager. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7916) Display available JDBC datasources as a dropdown menu

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7916?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7916: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Display available JDBC datasources as a dropdown menu > ----------------------------------------------------- > > Key: ISPN-7916 > URL: https://issues.jboss.org/browse/ISPN-7916 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha3 > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.4.0.Final > > > Currently the name of JDBC datasources are entered manually by the user, this should be replaced with a select option that consists of the configured datasources. > “/profile=clustered/subsystem=datasources/data-source=..." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7912) Prevent RocksDBStore writes blocking on full expiry queue

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7912?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7912: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Prevent RocksDBStore writes blocking on full expiry queue > --------------------------------------------------------- > > Key: ISPN-7912 > URL: https://issues.jboss.org/browse/ISPN-7912 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.4.0.Final > > > Currently you can only insert 10000 elements into the rocks db store until you will block a thread until the expiration reaper is ran. Instead we should offer elements to the queue and upon failure utilise the persistence executors to run purge. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7863) ISPN028501 (no property named) when access field after group by (by only certain char's)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7863?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7863: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > ISPN028501 (no property named) when access field after group by (by only certain char's) > ----------------------------------------------------------------------------------------- > > Key: ISPN-7863 > URL: https://issues.jboss.org/browse/ISPN-7863 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.0.0.Final > Reporter: Gregory Orciuch > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 9.4.0.Final > > > Links to: https://issues.jboss.org/browse/ISPN-7861 > When quering ISPN server over hotrod and trying to access field which begins with "v" character that field access is lost but together with "group by" operator. > Example of entity using proto/annotations: > {code:java} > @ProtoDoc("@Indexed") > public class Offering implements Serializable { > private String name; > private Integer relationSetId; > private Integer variant; > > @ProtoDoc("@Field(store = Store.YES, analyze = Analyze.YES)") > @ProtoField(number = 5, required = true) > public String getName() { > return name; > } > public void setName(String name) { > this.name = name; > } > > @ProtoField(number = 44) > public Integer getRelationSetId() { > return relationSetId; > } > public void setRelationSetId(Integer relationSetId) { > this.relationSetId = relationSetId; > } > > @ProtoDoc("@Field(store = Store.YES, analyze = Analyze.NO)") > @ProtoField(number = 50) > public Integer getVariant() { > return variant; > } > public void setVariant(Integer variant) { > this.variant = variant; > } > > } > {code} > Then executing query like this: > {code:sql} > select min(_gen0.name),min(_gen0.variant) FROM Offering _gen0 WHERE _gen0.variant = 44 GROUP BY _gen0.relationSetId > {code} > Produces server side error which mentions "ariant" - v - is lost. Paste is below. > NOT using group by is causing that query to run well. > ALSO Changing variable name from variant to "bariant" helps. > LOOKS like there is some code which restricts the name or parses wrongly. > Affects not only simple type fields but also List<Variant> variants - "v" is lost. > {panel:title=log} > 14:02:50,951 DEBUG [org.infinispan.query.dsl.embedded.impl.QueryEngine] (HotRod-ServerHandler-6-16) Building query 'select min(_gen0.name),min(_gen0.variant) FROM Offering _gen0 WHERE _gen0.variant = 44 GROUP BY _gen0.relationSetId' with parameters null > 14:02:50,953 DEBUG [org.infinispan.server.hotrod.HotRodExceptionHandler] (HotRod-ServerWorker-4-1) Exception caught: org.infinispan.objectfilter.ParsingException: ISPN028501: The type Offering has no property named '*ariant*'. > at org.infinispan.objectfilter.impl.syntax.parser.QueryResolverDelegateImpl.normalizeProperty(QueryResolverDelegateImpl.java:191) > at org.infinispan.objectfilter.impl.syntax.parser.QueryResolverDelegateImpl.normalizeUnqualifiedPropertyReference(QueryResolverDelegateImpl.java:84) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.unqualifiedPropertyReference(QueryResolver.java:7651) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.propertyReferencePath(QueryResolver.java:7548) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.propertyReferenceExpression(QueryResolver.java:5689) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.valueExpressionPrimary(QueryResolver.java:5495) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.valueExpression(QueryResolver.java:5271) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.rowValueConstructor(QueryResolver.java:4490) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.predicate(QueryResolver.java:3326) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.searchCondition(QueryResolver.java:2979) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.whereClause(QueryResolver.java:655) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.querySpec(QueryResolver.java:510) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.queryStatement(QueryResolver.java:379) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.queryStatementSet(QueryResolver.java:292) > at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.statement(QueryResolver.java:220) > at org.infinispan.objectfilter.impl.ql.QueryParser.resolve(QueryParser.java:81) > at org.infinispan.objectfilter.impl.ql.QueryParser.parseQuery(QueryParser.java:69) > at org.infinispan.objectfilter.impl.syntax.parser.IckleParser.parse(IckleParser.java:19) > at org.infinispan.query.dsl.embedded.impl.QueryEngine.lambda$parse$1(QueryEngine.java:663) > at org.infinispan.query.dsl.embedded.impl.QueryCache.lambda$get$0(QueryCache.java:79) > at org.infinispan.cache.impl.TypeConverterDelegatingAdvancedCache.lambda$convertFunction$1(TypeConverterDelegatingAdvancedCache.java:101) > at java.util.concurrent.ConcurrentMap.computeIfAbsent(ConcurrentMap.java:324) > at org.infinispan.cache.impl.AbstractDelegatingCache.computeIfAbsent(AbstractDelegatingCache.java:343) > at org.infinispan.cache.impl.TypeConverterDelegatingAdvancedCache.computeIfAbsent(TypeConverterDelegatingAdvancedCache.java:161) > at org.infinispan.query.dsl.embedded.impl.QueryCache.get(QueryCache.java:79) > at org.infinispan.query.dsl.embedded.impl.QueryEngine.parse(QueryEngine.java:663) > at org.infinispan.query.dsl.embedded.impl.QueryEngine.buildQueryWithAggregations(QueryEngine.java:299) > at org.infinispan.query.dsl.embedded.impl.QueryEngine.buildQuery(QueryEngine.java:139) > at org.infinispan.query.dsl.embedded.impl.DelegatingQuery.createQuery(DelegatingQuery.java:91) > at org.infinispan.query.dsl.embedded.impl.DelegatingQuery.list(DelegatingQuery.java:98) > at org.infinispan.query.remote.impl.QueryFacadeImpl.makeResponse(QueryFacadeImpl.java:61) > at org.infinispan.query.remote.impl.QueryFacadeImpl.query(QueryFacadeImpl.java:53) > at org.infinispan.server.hotrod.HotRodServer.query(HotRodServer.java:116) > at org.infinispan.server.hotrod.ContextHandler.realRead(ContextHandler.java:148) > at org.infinispan.server.hotrod.ContextHandler.lambda$null$0(ContextHandler.java:59) > at org.infinispan.security.Security.doAs(Security.java:143) > at org.infinispan.server.hotrod.ContextHandler.lambda$channelRead0$1(ContextHandler.java:58) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) > at java.lang.Thread.run(Thread.java:748) > {panel} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7861) ISPN028502: Unknown alias - when Group By with advanced where clause

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7861?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7861: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > ISPN028502: Unknown alias - when Group By with advanced where clause > -------------------------------------------------------------------- > > Key: ISPN-7861 > URL: https://issues.jboss.org/browse/ISPN-7861 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.0.0.Final > Reporter: Gregory Orciuch > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > Link to forum: [ISPN028502: Unknown alias - when Group By with advanced where clause|https://developer.jboss.org/thread/275039] > https://developer.jboss.org/thread/275039 > #freenode/infinispan > [17:06] <+anistor> GregoryO_: hi, looks like a bug. could you please file it in Jira? no need to copy the full description, just point to the forum. > [17:06] <+anistor> GregoryO_: thanks! > [17:06] <+anistor> GregoryO_: I'll have a look soon -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7859) Return proper 2XX codes in REST PUT/POST methods

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7859?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7859: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Return proper 2XX codes in REST PUT/POST methods > ------------------------------------------------ > > Key: ISPN-7859 > URL: https://issues.jboss.org/browse/ISPN-7859 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.4.0.Final > > > The REST interface currently returns only 200 on PUT/POST calls. We should adjust it to 201, 204 and 200. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7831) Administration console - adjust node memory graph to match PatternFly widget

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7831?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7831: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Administration console - adjust node memory graph to match PatternFly widget > ----------------------------------------------------------------------------- > > Key: ISPN-7831 > URL: https://issues.jboss.org/browse/ISPN-7831 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7982) Ickle purely negative fulltext subqueries cause empty results

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7982?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7982: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Ickle purely negative fulltext subqueries cause empty results > ------------------------------------------------------------- > > Key: ISPN-7982 > URL: https://issues.jboss.org/browse/ISPN-7982 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.Final > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > When using parethesis in an Ickle full text predicate, it can generate subqueries that are pure negative, e.g. > {{from IspnEvent where (tags : ('tagA' and (not 'a0')))}} > In Lucene, the query > {{+tags:taga +(-tags:a0)}} > is different from > {{+tags:taga -tags:a0}} > The latter works as expected, but the former brings empty results since Lucene does no support purely negative subqueries. In order for the former query to work, it needs to add all documents as another term to the subquery, for e.g. {{+tags:taga +(\*:\* -tags:a0)}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7979) Include all component licenses in distributions

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7979?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7979: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Include all component licenses in distributions > ----------------------------------------------- > > Key: ISPN-7979 > URL: https://issues.jboss.org/browse/ISPN-7979 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Tristan Tarrant > Assignee: Jakub Senko > Priority: Blocker > Fix For: 9.4.0.Final > > > The distributions should include licenses for all components -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018