Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8937CC0FF for ; Thu, 9 Aug 2012 16:42:11 +0000 (UTC) Received: (qmail 34007 invoked by uid 500); 9 Aug 2012 16:42:09 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 33940 invoked by uid 500); 9 Aug 2012 16:42:09 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 33930 invoked by uid 99); 9 Aug 2012 16:42:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Aug 2012 16:42:09 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_IMAGE_ONLY_28,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.48] (HELO mail-vb0-f48.google.com) (209.85.212.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Aug 2012 16:42:03 +0000 Received: by vbme21 with SMTP id e21so681039vbm.35 for ; Thu, 09 Aug 2012 09:41:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=nDghhuFauy0Nz2zDr5X5np+k+Nm2p7U/egDq+8JwHBk=; b=B4uDzbPv9xNSIFH3sfcr8ohRfYxhn1206Q8h/7OqAiVDcaLutGf6Gb3jxBlzA95J54 g6u862OMKHK4SceM6ULlX7etOfzdoS8JJ1eJoIAcDrBpLOBMHx1SVtbc1iJ3evsvELVW 4vhZUm8Jh+XjdCr8LF9Wk4US2tIkpUg9qbeVOkT4eCK37UMG859F5692sMzcjNzJaQbs 59XW4cFUzGnB9FGIA5+aU/6Olezvel1v90cdHbppfJerqyWY8ti4GWDTaAkFlmS3Ua24 4AqzOb10wnmWV5vAY3aiNaCNaLlT6wvL9Y1Qb9B1utHMEeSjWqAtKBZ0o0cYBQgFyVLc aMxQ== MIME-Version: 1.0 Received: by 10.52.66.225 with SMTP id i1mr2357237vdt.71.1344530501744; Thu, 09 Aug 2012 09:41:41 -0700 (PDT) Received: by 10.52.21.209 with HTTP; Thu, 9 Aug 2012 09:41:41 -0700 (PDT) In-Reply-To: References: <5023E00D.5050103@filez.com> Date: Thu, 9 Aug 2012 09:41:41 -0700 Message-ID: Subject: Re: serializable writables - HADOOP-8619 From: Steve Loughran To: common-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf307d0220f239e404c6d7e686 X-Gm-Message-State: ALoCoQk1mxYZsMp+pq6U1tmEvHTccEiTM3txC0NbJx3NiSyvfVZvPHRf8TXrkOpM9+w5aj+QZisz --20cf307d0220f239e404c6d7e686 Content-Type: text/plain; charset=UTF-8 correction: i'd like a junit test that pushes some of the std writables to an ObjectOutputStream and back, verifies round-tripping of data. It may seem extra work -but it stops serialization breaking in future. -steve On 9 August 2012 09:11, Steve Loughran wrote: > I've voted for it -ignoring the argument over wire protocols, there are > lots of other places in java where serialization is handy (e.g. servlet > state) > > ping me in a day or two if I don't commit it > > > On 9 August 2012 09:06, Radim Kolar wrote: > >> I really needs writables to be serializable for using cache on top of >> writables. >> >> https://issues.apache.org/**jira/browse/HADOOP-8619 >> >> can someone review this ticket and close it (as fixed or wont fix), i >> need to know final decision. >> > > > > -- > Steve Loughran > Hortonworks Inc > stevel@hortonworks.com > skype: steve_loughran > tel: +1 408 400 3721 > > > > > -- Steve Loughran Hortonworks Inc stevel@hortonworks.com skype: steve_loughran tel: +1 408 400 3721 --20cf307d0220f239e404c6d7e686--