Return-Path: 
 <user-return-716-apmail-crunch-user-archive=crunch.apache.org@crunch.apache.org>
X-Original-To: apmail-crunch-user-archive@www.apache.org
Delivered-To: apmail-crunch-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 EF87F17B60
	for <apmail-crunch-user-archive@www.apache.org>;
 Mon, 26 Jan 2015 21:16:10 +0000 (UTC)
Received: (qmail 95732 invoked by uid 500); 26 Jan 2015 21:16:11 -0000
Delivered-To: apmail-crunch-user-archive@crunch.apache.org
Received: (qmail 95685 invoked by uid 500); 26 Jan 2015 21:16:11 -0000
Mailing-List: contact user-help@crunch.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@crunch.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@crunch.apache.org>
List-Post: <mailto:user@crunch.apache.org>
List-Id: <user.crunch.apache.org>
Reply-To: user@crunch.apache.org
Delivered-To: mailing list user@crunch.apache.org
Received: (qmail 95675 invoked by uid 99); 26 Jan 2015 21:16:11 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2015 21:16:11 +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 (nike.apache.org: domain of dpo5003@gmail.com designates
 209.85.214.171 as permitted sender)
Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com)
 (209.85.214.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2015 21:15:45 +0000
Received: by mail-ob0-f171.google.com with SMTP id va2so10106436obc.2
        for <user@crunch.apache.org>; Mon, 26 Jan 2015 13:15:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=rFz/Fj2I5QkSEfCyfYrm5tE/8T3kx4we/akRrWYkF5o=;
        b=l+gDnrlhX9aFk+JPXPcpu6Fr2L1e3Izvb9igh5VIgivWVWvjejbSQeARd4xl3lOIUv
         IAoEXfl1Noz8JHILKfQ9gHg4XbzSLY2CrYvO4HHHxel5WvR2FLi1u3Jl2UiukuP0deu/
         eRKdHT7leKtdMPUZyRGifUbKwE5K73u6zv+RTDh5QzohDJnVQ20Yn3sKf0jOS6sLyKd6
         6AcAvb2HzykM2FOCg/UOHqZP4xm392Fw4wlTMAWI+SqCqwz60tc75MShgr5TVnl6tAMP
         G7dfeKDxMitX0Wnhsgs3/G4e4+1o414CIG0v6nvRVkdB26vs3JCNCf/yn8fBqQA55sqV
         jkLQ==
X-Received: by 10.182.165.202 with SMTP id za10mr13863048obb.8.1422306940491;
 Mon, 26 Jan 2015 13:15:40 -0800 (PST)
MIME-Version: 1.0
From: David Ortiz <dpo5003@gmail.com>
Date: Mon, 26 Jan 2015 21:15:40 +0000
Message-ID: 
 <CAC79LcbOdSUQseAhsRr-U2MPfGoJipQDw-e5WTLAnYL5N-BH7w@mail.gmail.com>
Subject: Output Sizing
To: user@crunch.apache.org
Content-Type: multipart/alternative; boundary=001a11c2ff0af33354050d94a30c
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c2ff0af33354050d94a30c
Content-Type: text/plain; charset=UTF-8

Hello,

     Is there any way to control output sizing on the crunch pipeline's
write method?  I am processing data which is written to s3 for a program
which cannot handle more than 10-20 MB per file, and am at a loss for how
to do this without writing a hive script to process the data.

Thanks,
     David Ortiz

--001a11c2ff0af33354050d94a30c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,<div><br></div><div>=C2=A0 =C2=A0 =C2=A0Is there any way to control o=
utput sizing on the crunch pipeline&#39;s write method?=C2=A0 I am processi=
ng data which is written to s3 for a program which cannot handle more than =
10-20 MB per file, and am at a loss for how to do this without writing a hi=
ve script to process the data.</div><div><br></div><div>Thanks,</div><div>=
=C2=A0 =C2=A0 =C2=A0David Ortiz</div>

--001a11c2ff0af33354050d94a30c--