Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2D68B100FB for ; Wed, 11 Sep 2013 19:19:36 +0000 (UTC) Received: (qmail 9662 invoked by uid 500); 11 Sep 2013 19:19:31 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 9563 invoked by uid 500); 11 Sep 2013 19:19:30 -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 9551 invoked by uid 99); 11 Sep 2013 19:19:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Sep 2013 19:19:30 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jayunit100@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Sep 2013 19:19:25 +0000 Received: by mail-la0-f46.google.com with SMTP id eh20so7715837lab.5 for ; Wed, 11 Sep 2013 12:19:04 -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=UXYMYM1rWtYZkuuqv4MKGjFdZ86OC1mv7o4SB9hcaeQ=; b=b5nB3ZEF0FyQS2X88WrTTgeig984IhxlTHtpgwh0yDkBmgQSFkX+e0DirmtLaWJj6t eTj+sR6gHQAJ0QQbBwRE7lbeDZNyBv3YqvaKVrXu+wUrpafhgtAKfivsRlH1Uy+zv16p L0exvt0EEfO0p+DFjxFmTWE4QJTT+/Ie4NjQXqI4ejK8+/ddzfRGyHTUT3qu3+mXVUB5 sJT8SW5rf4YhgW812S5XxX91mmupqJ3wqXwapiP02mFnHRy7KPPLJnbjnfbwd78CG5D3 GJU8n3vtMejnZpIakmYACMSxuGG4DwocLHZyGm3+a9dzBWB6Uzu6BfOUpt3LsHQ5YATv SZ2g== MIME-Version: 1.0 X-Received: by 10.112.158.225 with SMTP id wx1mr2788271lbb.37.1378927144398; Wed, 11 Sep 2013 12:19:04 -0700 (PDT) Received: by 10.112.126.231 with HTTP; Wed, 11 Sep 2013 12:19:04 -0700 (PDT) Date: Wed, 11 Sep 2013 15:19:04 -0400 Message-ID: Subject: Status of mapred* From: Jay Vyas To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11c349329cfa0a04e6207eae X-Virus-Checked: Checked by ClamAV on apache.org --001a11c349329cfa0a04e6207eae Content-Type: text/plain; charset=ISO-8859-1 Will 2.0+ hadoop continue supporting mapred* classes? Or are they being phased out. In particular, it appears to me that the RawLocalFileSystem doesnt work quite properly with mapred implementations that use the getPos() functionality inside of RecordReaders, and I was wondering wether I should look into the patch history of RawLocalFileSystem, or else, just consider mapred* libraries debunked and approaching irrelevance. -- Jay Vyas http://jayunit100.blogspot.com --001a11c349329cfa0a04e6207eae Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Will 2.0+ hadoop continue supporting mapred* classes?= =A0 Or are they being phased out.

In particular, it appears t= o me that the RawLocalFileSystem doesnt work quite properly with mapred imp= lementations that use the getPos() functionality inside of RecordReaders, a= nd I was wondering wether I should look into the patch history of RawLocalF= ileSystem, or else, just consider mapred* libraries debunked and approachin= g irrelevance.
--001a11c349329cfa0a04e6207eae--