[infinispan-issues] [JBoss JIRA] (ISPN-4200) ExampleConfigsTest.testRestRollingUpgrades fails

[Martin Gencur (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996062#comment-12996062 ] 

Martin Gencur commented on ISPN-4200:
-------------------------------------

Some additional notes:
I think the raw-values configuration parameter should be removed in the future as it's not currently configurable in server and its role is not very clear. This parameter seems useless.
As for writing and reading data via HotRod when there's a REST store configured, the ideal solution would have to cope with all clients in compatibility mode - HotRod, Memcached, embedded and there are various problems:
* It is not possible to transparently read data via HotRod on the target node as the REST store in use retrieves Java objects from the source node either as XML (current solution) or as a byte array which was created by ObjectOutputStream. So when HotRod reads such data, the client application would always have to perform additional deserialization. Writing data by HotRod on the target node (and writing them back to the source nodes via REST store  is problematic too. Even if we guess the MIME type to use (remember, we store via HotRod, no Mime type available), the data will always be serialized on the source node (REST store always sends byte array data), and a HotRod client that would like to read the data would have to perform additional deserialization. This is not what users would expect in compatibility mode.
* Similar problems would be when using embedded cache. There would be additional deserialization needed at some points,.

This is an overly complicated scenario with many moving parts and the solution would never be ideal. Maybe it's better to discourage from using different types of clients when there's a REST store included. The REST store's primary purpose is to allow for rolling upgrades with REST clients.

And the raw-values parameters seems redundant and should be deprecated and removed later.

> ExampleConfigsTest.testRestRollingUpgrades fails
> ------------------------------------------------
>
>                 Key: ISPN-4200
>                 URL: https://issues.jboss.org/browse/ISPN-4200
>             Project: Infinispan
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite - Server
>            Reporter: Jakub Markos
>            Assignee: Mircea Markus
>
> Fails in the latest snapshot on line 240 with 
> {code}
> Can't access etries stored in source node (target's RestCacheStore). expected:<value1> but was:<[B at 19676adb>
> {code}
> you can run the test from /server/integration/testsuite with this command:
> mvn clean test -Psuite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades
> The configs used are /server/integration/testsuite/target/server/node1/standalone/configuration/examples/{standalone-rest-rolling-upgrade.xml, standalone-compatibility-mode.xml}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)