[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 Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-5561?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-5561:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/3570
> 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.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, 3 months
[JBoss JIRA] (ISPN-5586) TestResourceTracker.backgroundTestStarted(this) doesn't work from the IDE
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5586:
----------------------------------
Summary: TestResourceTracker.backgroundTestStarted(this) doesn't work from the IDE
Key: ISPN-5586
URL: https://issues.jboss.org/browse/ISPN-5586
Project: Infinispan
Issue Type: Bug
Components: Core, Test Suite - Core
Affects Versions: 7.2.3.Final, 8.0.0.Alpha2
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.0.0.Beta1
When running from an IDE, {{UnitTestTestNGListener}} doesn't (usually) run, so the current test name isn't set on the main thread. ({{TestResourceTracker.getCurrentTestName()}} returns "main").
Calling {{TestResourceTracker.backgroundTestStarted()}} on a worker thread sets the proper test name, and because of {{TEST_PING}}, the cache managers started from the main thread and the worker thread can't join the same cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (ISPN-5584) Support fine-grained write skew check for FineGrainedAtomicMap entries
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5584:
----------------------------------
Summary: Support fine-grained write skew check for FineGrainedAtomicMap entries
Key: ISPN-5584
URL: https://issues.jboss.org/browse/ISPN-5584
Project: Infinispan
Issue Type: Feature Request
Components: Core
Affects Versions: 7.2.3.Final, 8.0.0.Alpha2
Reporter: Dan Berindei
Fix For: 8.0.0.Final
FineGrainedAtomicMap doesn't currently work with write skew check enabled.
I was able to make it work by adding a special case for DeltaAwareCacheEntry in WriteSkewHelper, however the map has a single version, so the write skew check fails if any of the sub-keys were modified in parallel. With pessimistic locking, fine-grained maps allow the user to modify different sub-keys concurrently, we should allow the same with optimistic locking.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months