Return-Path: X-Original-To: apmail-pig-dev-archive@www.apache.org Delivered-To: apmail-pig-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4DE6ED1F4 for ; Tue, 19 Feb 2013 23:19:13 +0000 (UTC) Received: (qmail 10042 invoked by uid 500); 19 Feb 2013 23:19:13 -0000 Delivered-To: apmail-pig-dev-archive@pig.apache.org Received: (qmail 9984 invoked by uid 500); 19 Feb 2013 23:19:12 -0000 Mailing-List: contact dev-help@pig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pig.apache.org Delivered-To: mailing list dev@pig.apache.org Received: (qmail 9971 invoked by uid 500); 19 Feb 2013 23:19:12 -0000 Delivered-To: apmail-hadoop-pig-dev@hadoop.apache.org Received: (qmail 9968 invoked by uid 99); 19 Feb 2013 23:19:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 23:19:12 +0000 Date: Tue, 19 Feb 2013 23:19:12 +0000 (UTC) From: "Cheolsoo Park (JIRA)" To: pig-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (PIG-3131) Document PluckTuple UDF MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PIG-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheolsoo Park reopened PIG-3131: -------------------------------- This broke the build: https://builds.apache.org/job/Pig-trunk/1414/ I will attach a fix. > Document PluckTuple UDF > ----------------------- > > Key: PIG-3131 > URL: https://issues.apache.org/jira/browse/PIG-3131 > Project: Pig > Issue Type: Task > Affects Versions: 0.12 > Reporter: Jonathan Coveney > Assignee: Russell Jurney > Priority: Blocker > Fix For: 0.12 > > Attachments: PIG-3131-hotfix.patch, PIG-3131.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira