[JBoss JIRA] (ISPN-7825) Conditional removes not propagating to indexes
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-7825:
---------------------------------------
Summary: Conditional removes not propagating to indexes
Key: ISPN-7825
URL: https://issues.jboss.org/browse/ISPN-7825
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying
Affects Versions: 9.0.0.Final
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
When doing a cache.remove(K, V) and the command succeeds, the value is not removed from the indexes.
Queries still return the correct results since after the query execution, the ids retrieved from Lucene that are not existent in the cache get discarded.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7824) RemoteCache lacks executeAsync
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-7824:
--------------------------------------
Summary: RemoteCache lacks executeAsync
Key: ISPN-7824
URL: https://issues.jboss.org/browse/ISPN-7824
Project: Infinispan
Issue Type: Enhancement
Components: Remote Protocols
Affects Versions: 9.0.0.Final, 8.2.6.Final
Reporter: Galder Zamarreño
Whereas there's a `putAsync` to complement `put`, there's no `executeAsync` to complement `execute`.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7823) RemoteCacheManager can block waiting to connect/ping
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-7823:
--------------------------------------
Summary: RemoteCacheManager can block waiting to connect/ping
Key: ISPN-7823
URL: https://issues.jboss.org/browse/ISPN-7823
Project: Infinispan
Issue Type: Enhancement
Components: Remote Protocols
Affects Versions: 9.0.0.Final, 8.2.6.Final
Reporter: Galder Zamarreño
When running Java Hot Rod client on top sensitive environments to blocking, e.g. Vert.x, you realise that the RemoteCacheManager constructor blocks.
This is due to the fact that RCM constructor waits to establish connections with the initial servers and sends pings on startup.
You can avoid RCM doing this by passing start=false as parameter and then calling start() manually, but start() is a blocking method.
So, we should have an alternative start() method that returns a CompletableFuture, hence avoiding any blocking.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7822) Move transaction classes to commons
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-7822:
---------------------------------
Summary: Move transaction classes to commons
Key: ISPN-7822
URL: https://issues.jboss.org/browse/ISPN-7822
Project: Infinispan
Issue Type: Sub-task
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
The transaction implementation that will be common to embedded and client/server can be moved to the commons package to avoid duplicate all the code.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7405) DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-7405?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-7405:
-----------------------------------------------
Jakub Senko <jsenko(a)redhat.com> changed the Status of [bug 1428027|https://bugzilla.redhat.com/show_bug.cgi?id=1428027] from POST to MODIFIED
> DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors
> ---------------------------------------------------------------------------------------
>
> Key: ISPN-7405
> URL: https://issues.jboss.org/browse/ISPN-7405
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying, Server
> Affects Versions: 9.0.0.Beta2
> Reporter: Adrian Nistor
> Assignee: Dan Berindei
> Priority: Blocker
> Fix For: 9.0.0.CR2
>
> Attachments: error.log
>
>
> Start an infinispan server and run the following CLI command:
> ./bin/ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=local:register-proto-schemas(file-names=[myFileWithSyntaxErrors.proto], file-contents=[kaboom])'
> since the file has syntax errors it should still be placed in the ___protobuf_metadata cache and a myFileWithSyntaxErrors.proto.errors key should also be created. No exception should be thrown. Currently no key is written in cache and the NPE from the attached log happens.
> When registering a proper file without syntax errors this works correctly.
> The problem disappears if I disable global state persistence, so the cachestore seems to play a role in this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months