Return-Path: Delivered-To: apmail-hadoop-pig-dev-archive@www.apache.org Received: (qmail 23384 invoked from network); 6 Jan 2009 01:26:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jan 2009 01:26:05 -0000 Received: (qmail 91637 invoked by uid 500); 6 Jan 2009 01:26:05 -0000 Delivered-To: apmail-hadoop-pig-dev-archive@hadoop.apache.org Received: (qmail 91617 invoked by uid 500); 6 Jan 2009 01:26:05 -0000 Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: pig-dev@hadoop.apache.org Delivered-To: mailing list pig-dev@hadoop.apache.org Received: (qmail 91606 invoked by uid 99); 6 Jan 2009 01:26:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2009 17:26:05 -0800 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; Tue, 06 Jan 2009 01:26:04 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 30FA5234C47E for ; Mon, 5 Jan 2009 17:25:44 -0800 (PST) Message-ID: <97502899.1231205144186.JavaMail.jira@brutus> Date: Mon, 5 Jan 2009 17:25:44 -0800 (PST) From: "Olga Natkovich (JIRA)" To: pig-dev@hadoop.apache.org Subject: [jira] Updated: (PIG-558) Distinct followed by a Join results in Invalid size 0 for a tuple error In-Reply-To: <530651974.1228530584214.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-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olga Natkovich updated PIG-558: ------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) patch committed; thanks, pradeep > Distinct followed by a Join results in Invalid size 0 for a tuple error > ----------------------------------------------------------------------- > > Key: PIG-558 > URL: https://issues.apache.org/jira/browse/PIG-558 > Project: Pig > Issue Type: Bug > Components: impl > Affects Versions: types_branch > Reporter: Viraj Bhat > Assignee: Pradeep Kamath > Fix For: types_branch > > Attachments: PIG-558-additional.patch, PIG-558.patch, table1, table2 > > > The following Pig script does a right outer join after the DISTINCT. > {code} > nonuniqtable1 = LOAD 'table1' AS (f1:chararray); > table1 = DISTINCT nonuniqtable1; > table2 = LOAD 'table2' AS (f1:chararray, f2:int); > temp = COGROUP table1 BY f1 INNER, table2 BY f1; > DESCRIBE temp; > explain temp; > dump temp; > {code} > ======================================================================================================== > It results in the following error. This is true for other join types as well. > ======================================================================================================== > java.io.IOException: Invalid size 0 for a tuple > at org.apache.pig.data.DataReaderWriter.readDatum(DataReaderWriter.java:57) > at org.apache.pig.data.DataReaderWriter.readDatum(DataReaderWriter.java:62) > at org.apache.pig.builtin.BinStorage.getNext(BinStorage.java:90) > at org.apache.pig.backend.executionengine.PigSlice.next(PigSlice.java:103) > at org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.SliceWrapper$1.next(SliceWrapper.java:157) > at org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.SliceWrapper$1.next(SliceWrapper.java:133) > at org.apache.hadoop.mapred.MapTask$TrackedRecordReader.next(MapTask.java:165) > at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:45) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:227) > at org.apache.hadoop.mapred.TaskTracker$Child.main(TaskTracker.java:2209) > ======================================================================================================== -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.