Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71A4018C76 for ; Fri, 18 Dec 2015 17:34:23 +0000 (UTC) Received: (qmail 64081 invoked by uid 500); 18 Dec 2015 17:34:23 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 64037 invoked by uid 500); 18 Dec 2015 17:34:23 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 64025 invoked by uid 99); 18 Dec 2015 17:34:22 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2015 17:34:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4C408C8FA5 for ; Fri, 18 Dec 2015 17:34:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.98 X-Spam-Level: ** X-Spam-Status: No, score=2.98 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3rxylE9ObaNg for ; Fri, 18 Dec 2015 17:34:16 +0000 (UTC) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 18BD720400 for ; Fri, 18 Dec 2015 17:34:16 +0000 (UTC) Received: by mail-lf0-f53.google.com with SMTP id y184so77037480lfc.1 for ; Fri, 18 Dec 2015 09:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yMoRpLCKYlxlMOS+LCijJO0xIUpZbErnJ0BNT80d2Go=; b=jWZuLk93EIVFpuDk0Nbat3N6X5nKQiRxOp3HCKYpqnsaRnQOVyVfNSUbbGVN2PsAvo EQ3muH/Kwvjnuau4tw3p6wK6AEZPrTnw4BkkR9/rawu/ccKvQPkClMO6AIECQwPQAEhH l9ghlyk7KXkhb9F61UHjOV+Zu3+cbXt2lsfcauj4yYANL33iTbRbAq4Ivuv+V8jITg9X 86KoytZqKxZ5sO3S3hMUv7WqHAjitFfTvJG26RwaE37l3XkVNqFk17qd1ic0FG4L+bhu CUdjnjaSfRNL7O7BKFopefRwmgWCAue0kdjwKSnpREPi41Ej1LolPrx5Dk+Qfm2AguuM 6yGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=yMoRpLCKYlxlMOS+LCijJO0xIUpZbErnJ0BNT80d2Go=; b=S7fcH9RQ3nd4fe0xoWvtOs0/lMvZXNMpizPgwpi9jHCNvmU8jlF/VtTEXpe6wYWsxi vox6FlMnJlc3C7o7YL+VHiv3Y9/wLo+fr7sl5mu0fe+IoPJptaTSOQ8/GL7BXFbQLQ37 gYfIVh11lOGUh1/AenZfkJD0K5b9PL3vSCHM/kF8crM6dPkkN704ihwTETSx+OcpzuNz eMLtMVPiL2f0Jn5KkcpjlRJfqNMeXAAZe18nAdIytMqCY6aIWpKMBpvKa68kJCBzDdWz TXfFv/3USG/VW/ET5OVMTIRDa7xVmUJEespwybKNsrNgVaOV8uSfyw0C5K7VRMNAFnaU qNvw== X-Gm-Message-State: ALoCoQm5DBlOzWRjZbv0gmp992ZpuIOnuw8DUz1vuNaRbNi5STMl/5bSMtswsUbe7L6Q6nCpz4T8ZTQRqSa0pmrNp57YPg4knBNWqPoY0HsxmbXNpP2BncU= MIME-Version: 1.0 X-Received: by 10.25.90.131 with SMTP id o125mr2036029lfb.120.1450460054324; Fri, 18 Dec 2015 09:34:14 -0800 (PST) Received: by 10.114.77.102 with HTTP; Fri, 18 Dec 2015 09:34:14 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Dec 2015 20:34:14 +0300 Message-ID: Subject: Re: CacheEntry serialization failure From: Vladimir Ozerov To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary=001a1141fcee4ccb6705272f8c79 --001a1141fcee4ccb6705272f8c79 Content-Type: text/plain; charset=UTF-8 I fixed the problem, it was a bug actually. By default classes which has some custom Java logic (e.g. Externalizable, or with writeObject/readObject methods) will be written using OptimizedMarshaller, so similar field names is not a problem. If you want to serialize such class in binary format and have duplicate field names, you should provide your own BinarySerializer, which will write these fields with different names. On Fri, Dec 18, 2015 at 8:07 PM, Andrey Kornev wrote: > How am I supposed to handle this situation if the class comes from a 3d > party I can't modify? > > Thanks > Andrey > > > Date: Fri, 18 Dec 2015 09:12:22 +0300 > > Subject: Re: CacheEntry serialization failure > > From: vozerov@gridgain.com > > To: dev@ignite.apache.org > > > > I'll take a look. > > > > On Fri, Dec 18, 2015 at 4:37 AM, Valentin Kulichenko < > > valentin.kulichenko@gmail.com> wrote: > > > > > Folks, > > > > > > It looks like CacheEntry implementation (i.e., the entry that contains > > > version) can't be properly serialized with the BinaryMarshaller. I > created > > > the test and the ticket: > https://issues.apache.org/jira/browse/IGNITE-2203 > > > > > > Can someone take a look? > > > > > > -Val > > > > > --001a1141fcee4ccb6705272f8c79--