[JBoss JIRA] (ISPN-6419) Drop hibernate-hql-lucene dependency, generate the lucene query directly
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-6419:
-----------------------------------
Summary: Drop hibernate-hql-lucene dependency, generate the lucene query directly
Key: ISPN-6419
URL: https://issues.jboss.org/browse/ISPN-6419
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying, Remote Querying
Affects Versions: 9.0.0.Final, 9.0.0.Alpha1
Reporter: Adrian Nistor
Assignee: Adrian Nistor
The Lucene query object should be generated from by visiting infinispan's AST instead of generating a jpql query string and passing it to hibernate-hql-lucene to generate the Lucene query object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-6418) Gather continuous query statistics
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-6418:
-----------------------------------
Summary: Gather continuous query statistics
Key: ISPN-6418
URL: https://issues.jboss.org/browse/ISPN-6418
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying, Remote Querying
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 9.0.0.Final, 9.0.0.Alpha1
Compute statistics similar to the ones provided by org.hibernate.search.jmx.StatisticsInfoMBean
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-6253) CancellationException is thrown in case if CompletableFuture task exits exceptionally
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6253?page=com.atlassian.jira.plugin.... ]
William Burns resolved ISPN-6253.
---------------------------------
Resolution: Duplicate Issue
This is fixed in ISPN-6392
> CancellationException is thrown in case if CompletableFuture task exits exceptionally
> -------------------------------------------------------------------------------------
>
> Key: ISPN-6253
> URL: https://issues.jboss.org/browse/ISPN-6253
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Anna Manukyan
>
> When the CompletableFuture runs on cluster and exits exceptionally, the real exception message is not visible. Instead CancellationException is shown, as given below:
> {code}
> java.util.concurrent.CancellationException
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:132)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:118)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.ExecuteOperation.executeOperation(ExecuteOperation.java:49)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:54)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.execute(RemoteCacheImpl.java:703)
> at org.infinispan.server.test.task.DistributedServerTaskIT.shouldThrowExceptionInRemoteTasks(DistributedServerTaskIT.java:107)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-6416) Index protobuf booleans as string instead of integer
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6416?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6416:
--------------------------------
Description: Booleans values used to be translated to 0/1 literals internally by the DSL builder in remote mode so the underlying Jpql query would differ for the same query in embedded vs remote mode which is not ideal.
> Index protobuf booleans as string instead of integer
> ----------------------------------------------------
>
> Key: ISPN-6416
> URL: https://issues.jboss.org/browse/ISPN-6416
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Final, 9.0.0.Alpha1
>
>
> Booleans values used to be translated to 0/1 literals internally by the DSL builder in remote mode so the underlying Jpql query would differ for the same query in embedded vs remote mode which is not ideal.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years