[infinispan-issues] [JBoss JIRA] (ISPN-8897) Indexes from different caches are mixed-up in server mode

[Gustavo Fernandes (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gustavo Fernandes updated ISPN-8897:
------------------------------------
    Description: 
When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index. 

This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:
{code:java}
remoteCache1.put(1, entity1)
remoteCache2.put(1, entity2)
{code}

The second call will replace the first indexed entry since the key is identical and the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.




  was:
When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index. 

This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:
{code:java}
remoteCache1.put(1, entity1)
remoteCache2.put(1, entity2)
{code}

The second call will replace the first indexed entry since the key is identical ans the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.






> Indexes from different caches are mixed-up in server mode
> ---------------------------------------------------------
>
>                 Key: ISPN-8897
>                 URL: https://issues.jboss.org/browse/ISPN-8897
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote Querying
>    Affects Versions: 9.1.6.Final, 9.2.0.Final
>            Reporter: Gustavo Fernandes
>            Assignee: Gustavo Fernandes
>
> When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity {{ProtobufValueWrapper}} to store the values in the index. 
> This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:
> {code:java}
> remoteCache1.put(1, entity1)
> remoteCache2.put(1, entity2)
> {code}
> The second call will replace the first indexed entry since the key is identical and the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)