Mailing-List: contact issues-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Thu, 26 Mar 2015 10:20:52 +0000 (UTC)
From: "Artem Shutak (JIRA)" <jira@apache.org>
To: issues@ignite.incubator.apache.org
Message-ID: <JIRA.12785835.1427364990000.35032.1427365252717@Atlassian.JIRA>
In-Reply-To: <JIRA.12785835.1427364990000@Atlassian.JIRA>
References: <JIRA.12785835.1427364990000@Atlassian.JIRA>
 <JIRA.12785835.1427364990726@arcas>
Subject: [jira] [Updated] (IGNITE-608) [Test] Fix cache with
 portableEnabled=true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/IGNITE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Shutak updated IGNITE-608:
--------------------------------
    Labels: failedtest  (was: )

> [Test] Fix cache with portableEnabled=true
> ------------------------------------------
>
>                 Key: IGNITE-608
>                 URL: https://issues.apache.org/jira/browse/IGNITE-608
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Yakov Zhdanov
>              Labels: failedtest
>             Fix For: sprint-3
>
>
> 1. Portable object must be deserialized before return to user (see cache 'get' implementation), looks like now it is not implemented for put/remove return value, peek, reload (need check all cache public API).
> 2. Need to make sure that all tests in GridCachePortableEnabledSelfTestSuite pass (add suite to TC after that).
> Comment from GG-8743:
> - Fixed all found issues with portables except metadata update inside explicit transaction. If metadata is updated then method GridEntPortableProcessor.addMeta is called which can execute 'invoke' on system cache. For now just changed it to execute invoke in another thread (using 'CU.outTx'). Is it possible to add internal method to execute 'invoke' without enlisting system cache in transaction? If this is not easy to add I think we can leave it as is since metadata update is not expecte to happen frequently.
> See GG-9271 and GG-8743. Also see TODOs in java-code for this issue


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)