May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6588) Query DSL like queries should only accept % and _ as the wildcards

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6588?page=com.atlassian.jira.plugin.... ] Work on ISPN-6588 started by Adrian Nistor. ------------------------------------------- > Query DSL like queries should only accept % and _ as the wildcards > ------------------------------------------------------------------ > > Key: ISPN-6588 > URL: https://issues.jboss.org/browse/ISPN-6588 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The official wildcards are % and _. But users can mistakenly use * and ? and those will usually work too. This works because the * and ? are valid wildcards in the underlying Lucene query language. But this breaks if the query is supposed to be run un-indexed for whatever reason. > To fix this we need to escape * and ? from user's input so they are no longer internally handled by Lucene as wildcards. These chars should cause an exact match instead. The actual recognized wildcards should be only % and _. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6588) Query DSL like queries should only accept % and _ as the wildcards

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6588?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6588: -------------------------------- Status: Open (was: New) > Query DSL like queries should only accept % and _ as the wildcards > ------------------------------------------------------------------ > > Key: ISPN-6588 > URL: https://issues.jboss.org/browse/ISPN-6588 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The official wildcards are % and _. But users can mistakenly use * and ? and those will usually work too. This works because the * and ? are valid wildcards in the underlying Lucene query language. But this breaks if the query is supposed to be run un-indexed for whatever reason. > To fix this we need to escape * and ? from user's input so they are no longer internally handled by Lucene as wildcards. These chars should cause an exact match instead. The actual recognized wildcards should be only % and _. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6588) Query DSL like queries should only accept % and _ as the wildcards

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6588: ----------------------------------- Summary: Query DSL like queries should only accept % and _ as the wildcards Key: ISPN-6588 URL: https://issues.jboss.org/browse/ISPN-6588 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Alpha2, 8.2.2.Final The official wildcards are % and _. But users can mistakenly use * and ? and those will usually work too. This works because the * and ? are valid wildcards in the underlying Lucene query language. But this breaks if the query is supposed to be run un-indexed for whatever reason. To fix this we need to escape * and ? from user's input so they are no longer internally handled by Lucene as wildcards. These chars should cause an exact match instead. The actual recognized wildcards should be only % and _. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6576) Functional API does not load values from cache loader on non-primary owners

by Krzysztof Sobolewski (JIRA)

[ https://issues.jboss.org/browse/ISPN-6576?page=com.atlassian.jira.plugin.... ] Krzysztof Sobolewski updated ISPN-6576: --------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4303 (was: https://github.com/infinispan/infinispan/pull/4302) > Functional API does not load values from cache loader on non-primary owners > --------------------------------------------------------------------------- > > Key: ISPN-6576 > URL: https://issues.jboss.org/browse/ISPN-6576 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Krzysztof Sobolewski > Attachments: AbstractFunctionalCachestoreTest.java, AbstractFunctionalCachestoreTest.java, FunctionalCachestoreTestNonTx.java, FunctionalCachestoreTestTx.java > > > We have a cluster in DIST mode with numOwners > 1, so there are primary and secondary owners, with persistence enabled. When I do a read-write operation on the cluster using the Functional API on a key that is present in the cache loader, the entry that gets passed to the functional operation has a non-null value only for the primary owner. See: > org.infinispan.interceptors.ClusteredCacheLoaderInterceptor.skipLoadForWriteCommand() > line 53. > This is using non-transactional cache. > NOTE: The attached tests are modified version of the ones in ISPN-6573. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6576) Functional API does not load values from cache loader on non-primary owners

by Krzysztof Sobolewski (JIRA)

[ https://issues.jboss.org/browse/ISPN-6576?page=com.atlassian.jira.plugin.... ] Krzysztof Sobolewski updated ISPN-6576: --------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4302 > Functional API does not load values from cache loader on non-primary owners > --------------------------------------------------------------------------- > > Key: ISPN-6576 > URL: https://issues.jboss.org/browse/ISPN-6576 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Krzysztof Sobolewski > Attachments: AbstractFunctionalCachestoreTest.java, AbstractFunctionalCachestoreTest.java, FunctionalCachestoreTestNonTx.java, FunctionalCachestoreTestTx.java > > > We have a cluster in DIST mode with numOwners > 1, so there are primary and secondary owners, with persistence enabled. When I do a read-write operation on the cluster using the Functional API on a key that is present in the cache loader, the entry that gets passed to the functional operation has a non-null value only for the primary owner. See: > org.infinispan.interceptors.ClusteredCacheLoaderInterceptor.skipLoadForWriteCommand() > line 53. > This is using non-transactional cache. > NOTE: The attached tests are modified version of the ones in ISPN-6573. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6574) JCache CacheManger need to know about existing caches if remote (HotRod) is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6574?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-6574: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1332924 Bugzilla Update: Perform > JCache CacheManger need to know about existing caches if remote (HotRod) is used > -------------------------------------------------------------------------------- > > Key: ISPN-6574 > URL: https://issues.jboss.org/browse/ISPN-6574 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final > > > For a client which use the JCache API in combination with a Infinispan server it is expected that a getCache("MyCache") would return a reference to the existing cache or an Exception according to JSR-107 API. > Also the getCacheNames() enableManagement(..) and enableStatistic(...) should support this also. > Excerpt from API Doc: > ------------------------------------ > K,V> Cache<K,V> getCache(String cacheName, > Class<K> keyType, > Class<V> valueType) > Looks up a managed Cache given its name. > This method must be used for Caches that were configured with runtime key and value types. Use getCache(String) for Caches where these were not specified. > Implementations must ensure that the key and value types are the same as those configured for the Cache prior to returning from this method. > Implementations may further perform type checking on mutative cache operations and throw a ClassCastException if these checks fail. > Implementations that support declarative mechanisms for pre-configuring Caches may return a pre-configured Cache instead of null. > Parameters: > cacheName - the name of the managed Cache to acquire > keyType - the expected Class of the key > valueType - the expected Class of the value > Returns: > the Cache or null if it does exist or can't be pre-configured > Throws: > IllegalStateException - if the CacheManager is isClosed() > IllegalArgumentException - if the specified key and/or value types are incompatible with the configured cache. > SecurityException - when the operation could not be performed due to the current security settings -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6130) # Activations shows incorrect value

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6130?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-6130: ----------------------------------- It look ok to me and by the case described, the value 0 is expected. activation is only take into account when passivation=true and the key is in the cache store when the operation is performed. > # Activations shows incorrect value > ------------------------------------ > > Key: ISPN-6130 > URL: https://issues.jboss.org/browse/ISPN-6130 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Martin Vrabel > Assignee: Pedro Ruivo > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain evictions size=10 > In the Entries lifecycle" tab, there is a field "# Activations" which should show number of Activations . When I put 10 entries in the cache and read 10, this field #Activations show 0 as is should. But when I insert another 10 entries (so the first 10 entries will evict and be stored in the cache store) and read the first 10 entries the #Activations field will show 0, but it should be 10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6114) Management console - node view - performance and caching activities are not calculated properly

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6114?page=com.atlassian.jira.plugin.... ] Pedro Zapata resolved ISPN-6114. -------------------------------- Resolution: Cannot Reproduce Bug That's apparently fixed in the latest releases > Management console - node view - performance and caching activities are not calculated properly > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6114 > URL: https://issues.jboss.org/browse/ISPN-6114 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Pedro Zapata > Attachments: screenshot-1.png, screenshot-2.png > > > Clusters tab -> click on cluster -> click on node > After doing operations on cache that is deployed on node the statistics (e.g. #PUTS) still display 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6114) Management console - node view - performance and caching activities are not calculated properly

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6114?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-6114: ------------------------------- Attachment: screenshot-2.png > Management console - node view - performance and caching activities are not calculated properly > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6114 > URL: https://issues.jboss.org/browse/ISPN-6114 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Pedro Zapata > Attachments: screenshot-1.png, screenshot-2.png > > > Clusters tab -> click on cluster -> click on node > After doing operations on cache that is deployed on node the statistics (e.g. #PUTS) still display 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6114) Management console - node view - performance and caching activities are not calculated properly

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6114?page=com.atlassian.jira.plugin.... ] Pedro Zapata commented on ISPN-6114: ------------------------------------ That's certainly not happening any more. See screenshot. > Management console - node view - performance and caching activities are not calculated properly > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6114 > URL: https://issues.jboss.org/browse/ISPN-6114 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Pedro Zapata > Attachments: screenshot-1.png > > > Clusters tab -> click on cluster -> click on node > After doing operations on cache that is deployed on node the statistics (e.g. #PUTS) still display 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016