Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35C3111C9D for ; Tue, 22 Apr 2014 11:17:10 +0000 (UTC) Received: (qmail 75234 invoked by uid 500); 22 Apr 2014 11:17:00 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 74876 invoked by uid 500); 22 Apr 2014 11:16:57 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 74869 invoked by uid 99); 22 Apr 2014 11:16:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2014 11:16:56 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,HTML_OBFUSCATE_05_10,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xiaotao.cs.nju@gmail.com designates 209.85.192.49 as permitted sender) Received: from [209.85.192.49] (HELO mail-qg0-f49.google.com) (209.85.192.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2014 11:16:50 +0000 Received: by mail-qg0-f49.google.com with SMTP id j5so4398939qga.22 for ; Tue, 22 Apr 2014 04:16:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=OsmluCn7XXljS93zpOWEHtUPqAdLTJmyb+EcyMAzCT8=; b=IpQDWV6B6cYZmzZ5S/RX/12Dv/omwNy0TSW9+Anntfn5VD+468f4RX77iNzn+pz7Dc MLu8i8uPVQvwpFNcAtrkBt5lFmTPO8LAPYZLFSOGt+g7W7qVRuPKSDE5XWf1uTAY8sn+ 7gXQsBjSuDEsK/J0VWUiiEdajxbsbjxpuHOJ9zoXU45sB++N1r+OsxatjECzGy6Wrbmo UaLRIMjyX+1Cu0qGZ+mHPvfb8GPbCA8QaSK+cegt6Nw8yWeOH7LkWt0PkiiaUUF5JamF oQMhPAStOu5TaKJ4t8K+Me4+Unp5xMZfQQ++rc1PDvoMxu8zmbB49uj05FTb+9IBPHYs wqJQ== MIME-Version: 1.0 X-Received: by 10.140.34.46 with SMTP id k43mr44908647qgk.63.1398165390272; Tue, 22 Apr 2014 04:16:30 -0700 (PDT) Received: by 10.96.213.228 with HTTP; Tue, 22 Apr 2014 04:16:30 -0700 (PDT) Date: Tue, 22 Apr 2014 19:16:30 +0800 Message-ID: Subject: Can we use Kryo instead of WritableSerialization to serialize objects in Hadoop? From: Tao Xiao To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c0502c6cad5604f79fbf6a X-Virus-Checked: Checked by ClamAV on apache.org --001a11c0502c6cad5604f79fbf6a Content-Type: text/plain; charset=UTF-8 The default implementation of serialization in Hadoop is *org.apache.hadoop.io.serializer.WritableSerialization*, but it is not so efficient as *Kryo*. Can we replace WritableSerialization with Kryo? How to do it ? --001a11c0502c6cad5604f79fbf6a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The default implementation of serialization in Hadoop is=C2=A0org.apache.hadoop.io.serializer.Writa= bleSerialization, but it is not so efficient as Kryo.=C2=A0

Can w= e replace WritableSerialization with Kryo? How to do it ?
--001a11c0502c6cad5604f79fbf6a--