July 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4797) Use getAll for retrieving query results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4797?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4797: ----------------------------------------------- Gustavo Fernandes <gfernand(a)redhat.com> changed the Status of [bug 1148727|https://bugzilla.redhat.com/show_bug.cgi?id=1148727] from NEW to MODIFIED > Use getAll for retrieving query results > --------------------------------------- > > Key: ISPN-4797 > URL: https://issues.jboss.org/browse/ISPN-4797 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Fix For: 7.2.0.Final > > > (as soon as getAll will be implemented) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5412) Native Spark Connector

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5412?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5412: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-spark/pull/1 > Native Spark Connector > ---------------------- > > Key: ISPN-5412 > URL: https://issues.jboss.org/browse/ISPN-5412 > Project: Infinispan > Issue Type: Feature Request > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > A RDD implementation with best data locality would allow directly access to Infinispan from Spark, without involving Hadoop. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5635) Upgrade server to WildFly 9.0.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5635?page=com.atlassian.jira.plugin.... ] Work on ISPN-5635 stopped by Tristan Tarrant. --------------------------------------------- > Upgrade server to WildFly 9.0.1.Final > ------------------------------------- > > Key: ISPN-5635 > URL: https://issues.jboss.org/browse/ISPN-5635 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5635) Upgrade server to WildFly 9.0.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5635?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5635: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3609 > Upgrade server to WildFly 9.0.1.Final > ------------------------------------- > > Key: ISPN-5635 > URL: https://issues.jboss.org/browse/ISPN-5635 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5636) Test server modules against WildFly 10 Alpha

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5636?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5636: ---------------------------------- Status: Open (was: New) > Test server modules against WildFly 10 Alpha > -------------------------------------------- > > Key: ISPN-5636 > URL: https://issues.jboss.org/browse/ISPN-5636 > Project: Infinispan > Issue Type: Component Upgrade > Components: WildFly modules > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5636) Test server modules against WildFly 10 Alpha

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5636?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5636: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3609 > Test server modules against WildFly 10 Alpha > -------------------------------------------- > > Key: ISPN-5636 > URL: https://issues.jboss.org/browse/ISPN-5636 > Project: Infinispan > Issue Type: Component Upgrade > Components: WildFly modules > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5635) Upgrade server to WildFly 9.0.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5635?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5635: ---------------------------------- Status: Open (was: New) > Upgrade server to WildFly 9.0.1.Final > ------------------------------------- > > Key: ISPN-5635 > URL: https://issues.jboss.org/browse/ISPN-5635 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5635) Upgrade server to WildFly 9.0.1.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5635?page=com.atlassian.jira.plugin.... ] Work on ISPN-5635 started by Tristan Tarrant. --------------------------------------------- > Upgrade server to WildFly 9.0.1.Final > ------------------------------------- > > Key: ISPN-5635 > URL: https://issues.jboss.org/browse/ISPN-5635 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 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 Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5561?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5561: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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: 7.2.4.Final, 8.0.0.CR1, 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)

9 years, 5 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 Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5561?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5561: ------------------------------- Fix Version/s: 8.0.0.Beta2 (was: 8.0.0.CR1) > 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)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2015