August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5656) Drop the server 5.3 parser

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5656?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5656: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Drop the server 5.3 parser > -------------------------- > > Key: ISPN-5656 > URL: https://issues.jboss.org/browse/ISPN-5656 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.Beta3 > > > The 5.3 server parser doesn't need to stay around -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4919) Configuration templates

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4919: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Configuration templates > ----------------------- > > Key: ISPN-4919 > URL: https://issues.jboss.org/browse/ISPN-4919 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.Beta3 > > > Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not. > We should introduce the concept of configuration inheritance, e.g.: > {code} > <local-cache name="eviction-cache"> > <eviction strategy="LIRS" maxEntries="10000"/> > </local-cache> > <local-cache name="mycache" template="eviction-cache" /> > {code} > Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.: > {code} > <local-cache name="eviction-cache" abstract="true"> > ... > </local-cache> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5222) Perform Remote Filtering/Conversion in a single step

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5222?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5222: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1211944|https://bugzilla.redhat.com/show_bug.cgi?id=1211944] from ON_QA to VERIFIED > Perform Remote Filtering/Conversion in a single step > ---------------------------------------------------- > > Key: ISPN-5222 > URL: https://issues.jboss.org/browse/ISPN-5222 > Project: Infinispan > Issue Type: Feature Request > Components: Listeners > Affects Versions: 7.1.0.Final > Reporter: Stylianos Koussouris > Assignee: Galder Zamarreño > Fix For: 7.2.0.Final > > > I want to have filter and convert take place in one step ie. do filtering and conversion applied to REMOTE LISTENERS in one step > a) I define CacheEventConverterFactory which implements CacheEventConverterFactory, Serializable > b) I register on the server org.infinispan.notifications.cachelistener.filter.CacheEventConverterFactory the cache event converter > which returns (CacheEventConverter<K, V, C>) new SharesDynamicFilterConverter(params); > c) I then define CacheEventFilterFactory which implements CacheEventFilterFactory, Serializable { > and returns(CacheEventFilter<K, V>) new SharesDynamicFilterConverter(params); > d) The CustomeDynamicFilterConverter extends AbstractCacheEventFilterConverter<String, Share, ShareProgress> implements Serializable { > and has the implementation of > public Share filterAndConvert(String key, Share oldValue, Metadata oldMetadata, Share newValue, Metadata newMetadata, EventType eventType) { > e) finally I define a listener binding it to the filter and converter > @ClientListener(filterFactoryName = "custom-dynamic-filter", > converterFactoryName = "custom-dynamic-converter", > includeCurrentState = true) > and register it along with params for the filter on the client side > cache.addClientListener(listener, new Object[]{"NYX", 50f}, null); > The result of this is that certainly both accept and convert methods are run and both call the same filterAndConvert method on SharesDynamicFilterConverter > However, this is not desirable as I don't want 2 steps which will effectively do the same thing but a single step. TBH I am not happy with the solution but what I did (in absence of better understanding of how to combine the steps -NOTE there is no single Factory for both Converter and Filter and even if it did we would probably have to implement accept & convert inside so the end result would have been the same) > So what I did was to change the last step > ie. > e) finally I define a listener binding ONLY the converter > @ClientListener(converterFactoryName = "murex-dynamic-converter", includeCurrentState = true) > and register it along with params ONLY for the converter on the client side > cache.addClientListener(listener, null, new Object[]{"NYX", 50f}); > This works as it actually does the filter during the convert step BUT is there another way and am I missing something? If not this would be a feature request -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5392) ComparisonExpr.Type.negate() returns wrong value

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5392?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5392: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1211944|https://bugzilla.redhat.com/show_bug.cgi?id=1211944] from ON_QA to VERIFIED > ComparisonExpr.Type.negate() returns wrong value > ------------------------------------------------ > > Key: ISPN-5392 > URL: https://issues.jboss.org/browse/ISPN-5392 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.2.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Final > > > The value returned for Type.GREATER should be LESS_OR_EQUAL but it wrongly returns LESS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5350) Use DSL based filters with Hot Rod event listeners

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5350?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5350: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1211944|https://bugzilla.redhat.com/show_bug.cgi?id=1211944] from ON_QA to VERIFIED > Use DSL based filters with Hot Rod event listeners > -------------------------------------------------- > > Key: ISPN-5350 > URL: https://issues.jboss.org/browse/ISPN-5350 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5349) Use DSL based filters with local and clustered event listeners

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5349?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5349: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1211944|https://bugzilla.redhat.com/show_bug.cgi?id=1211944] from ON_QA to VERIFIED > Use DSL based filters with local and clustered event listeners > -------------------------------------------------------------- > > Key: ISPN-5349 > URL: https://issues.jboss.org/browse/ISPN-5349 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5388?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5388: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1211944|https://bugzilla.redhat.com/show_bug.cgi?id=1211944] from ON_QA to VERIFIED > Optimize redundant predicates (non-indexed query) > ------------------------------------------------- > > Key: ISPN-5388 > URL: https://issues.jboss.org/browse/ISPN-5388 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: > * X || X => X > * X && X => X > * !X || !X => !X > * !X && !X => !X > * X || !X => TRUE (tautology) > * X && !X => FALSE (contradiction) > (where X is a predicate not a general boolean expression) > Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5347) Extend org.infinispan.objectfilter.Matcher to support event types and user context data

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5347?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5347: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1211944|https://bugzilla.redhat.com/show_bug.cgi?id=1211944] from ON_QA to VERIFIED > Extend org.infinispan.objectfilter.Matcher to support event types and user context data > --------------------------------------------------------------------------------------- > > Key: ISPN-5347 > URL: https://issues.jboss.org/browse/ISPN-5347 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > The Matcher should accept a user context object and an event type object beside the instance being tested and should pass the user context and event type to the callback of the matching subscriptions. The user context object and event type should be optional. > Also, when subscribing the user should be able to specify an optional event type. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5561) Problem in dealing with the HQL queries that contain string comparison operations, when it involves empty string as an operand

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5561?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5561: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1238866|https://bugzilla.redhat.com/show_bug.cgi?id=1238866] from ASSIGNED to VERIFIED > Problem in dealing with the HQL queries that contain string comparison operations, when it involves empty string as an operand > ------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-5561 > URL: https://issues.jboss.org/browse/ISPN-5561 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 7.2.0.Final > Environment: Infinispan version: Infinispan 7.2.0-Final > Operating System: Linux > Compatibility mode is enabled. > Indexing is enabled and 'autoconfig' parameter is set to true. > Reporter: Pavan Kundgol > Assignee: Adrian Nistor > Fix For: 8.0.0.Beta2, 7.2.4.Final, 8.0.0.Final > > > When a HQL query that involves string comparison operation with the empty string matching is executed through hot rod client(java), it is resulting in the following error, > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[7] returned server error (status=0x85): org.hibernate.search.exception.EmptyQueryException: HSEARCH000146: The query string '' applied on field 'CITY' has no meaningful tokens to be matched. Validate the query input against the Analyzer applied on this field. > The same problem may also occur when the string matching operation involves a string containing certain special keywords(hibernate search stop words), as operands. > The problem seems to be assosiated with the the 'hibernate-hql-lucene' parser used by the 'infinispan-remote-query-server' module. The problem here is that the hibernate-hql-lucene parser is translating comparison operations directly into lucene keyword matching operations, irrespective of the field type, though the phrase matching is more appropriate for string fields. This leads to invalid query formation when the field in concern is of type string, and is matched against an empty string(or a string containing one or more hibernate search stop words). > For example, > the where condition city='' present in the following HQL query > select name from com.test.User where city='' > is tralated to lucene query, the hql-lucene parser is currently translating to > queryBuilder.keyword().onField("city").matching("").createQuery() > whereas recommended one is > queryBuilder.phrase().onField("city").sentence("").createQuery() > In the former way of translation, Hibernate Search query execution fails due to its usage of standard analyzer while executing the query. Hence, the problem can also be avoided by disabling the standard analyzer while executing the query. > queryBuilder.keyword().onField("city").ignoreAnalyzer().matching("").createQuery() > Preferred solution may be to enhance the 'hibernate-hql-lucene' library to do type specific translations, and to specifically translate the string comparison operations of hql query into phrase matching operations of lucene query(instead of keyword matching operations). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5596) "Cannot clear data directory" in SoftIndexFileStore when clear() is called after stopping and restarting cache

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5596?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-5596: ----------------------------------- Could you increase the timeouts in the code and check who's using that file using tool like Process Explorer? There could be windows indexing on on the drive you use as the storage... > "Cannot clear data directory" in SoftIndexFileStore when clear() is called after stopping and restarting cache > -------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5596 > URL: https://issues.jboss.org/browse/ISPN-5596 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 7.2.3.Final > Environment: Windows 7 > Reporter: Andreas Pabst > Assignee: Radim Vansa > Attachments: SoftIndexFileStoreTest.java, test.log, test2.log, test3.log > > > When stopping and restarting a cache with SoftIndexFileStore persistence, it behaves strangely. > Calling cache.clear() leads to the following exception: > ERROR: ISPN000136: Execution error > org.infinispan.persistence.spi.PersistenceException: Cannot clear data directory! > at org.infinispan.persistence.sifs.SoftIndexFileStore.clear(SoftIndexFileStore.java:234) > at org.infinispan.persistence.manager.PersistenceManagerImpl.clearAllStores(PersistenceManagerImpl.java:372) > at org.infinispan.interceptors.CacheWriterInterceptor.visitClearCommand(CacheWriterInterceptor.java:158) > ... > Caused by: java.io.IOException: Cannot delete file soft-index-test\data\2 > at org.infinispan.persistence.sifs.FileProvider.clear(FileProvider.java:205) > at org.infinispan.persistence.sifs.SoftIndexFileStore.clear(SoftIndexFileStore.java:232) > If the manager is also stopped and recreated every time, this only happens after the third iteration. > Calling cache.remove() in the same place leads to an unrecoverable corruption of the cache store files: java.lang.IllegalArgumentException: Negative position -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2015