Return-Path: Delivered-To: apmail-incubator-pig-dev-archive@locus.apache.org Received: (qmail 36270 invoked from network); 19 Mar 2008 21:14:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2008 21:14:17 -0000 Received: (qmail 747 invoked by uid 500); 19 Mar 2008 21:14:15 -0000 Delivered-To: apmail-incubator-pig-dev-archive@incubator.apache.org Received: (qmail 722 invoked by uid 500); 19 Mar 2008 21:14:15 -0000 Mailing-List: contact pig-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: pig-dev@incubator.apache.org Delivered-To: mailing list pig-dev@incubator.apache.org Received: (qmail 707 invoked by uid 99); 19 Mar 2008 21:14:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 14:14:15 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 21:13:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7EEA4234C0A6 for ; Wed, 19 Mar 2008 14:12:24 -0700 (PDT) Message-ID: <898378349.1205961144505.JavaMail.jira@brutus> Date: Wed, 19 Mar 2008 14:12:24 -0700 (PDT) From: "Pi Song (JIRA)" To: pig-dev@incubator.apache.org Subject: [jira] Commented: (PIG-94) Pig Streaming functional spec proposal In-Reply-To: <32233260.1202239207438.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/PIG-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580565#action_12580565 ] Pi Song commented on PIG-94: ---------------------------- 2) You're talking about synchronous and asynchronous mode right? - For synchronous mode, outputBytes really seems to be a good candidate - For asynchronous mode, how about we also monitor outputBytes but with much higher timeout default? So basically, we do the same thing but with different parameter. 3) I think Pig itself still doesn't have a good way to display execution errors. If there is a log file that we can access, that should be good enough for the time being. > Pig Streaming functional spec proposal > -------------------------------------- > > Key: PIG-94 > URL: https://issues.apache.org/jira/browse/PIG-94 > Project: Pig > Issue Type: New Feature > Reporter: Olga Natkovich > Assignee: Arun C Murthy > Attachments: patch.txt, PIG-94_1_1_20080304.patch, PIG-94_1_20080303.patch, PIG-94_2_0_20080317.patch, PigStreamingTestPlan.htm > > > This issue is for discussion about Pig streaming functional spec. > http://wiki.apache.org/pig/PigStreamingFunctionalSpec -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.