[jira] Updated: (PIG-366) PigPen - Eclipse plugin for a graphical PigLatin editor

[ https://issues.apache.org/jira/browse/PIG-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shubham Chopra updated PIG-366: --- Attachment: org.apache.pig.pigpen_0.0.4.jar Updated plugin jar. This addresses a lot of minor issues wit

[jira] Created: (PIG-668) parametere substitution truncates value if it has special character like "."

parametere substitution truncates value if it has special character like "." Key: PIG-668 URL: https://issues.apache.org/jira/browse/PIG-668 Project: Pig Issue Type

[jira] Created: (PIG-669) Bug in Schema comparison for casting

Bug in Schema comparison for casting Key: PIG-669 URL: https://issues.apache.org/jira/browse/PIG-669 Project: Pig Issue Type: Bug Environment: i686 i386 GNU/Linux Reporter: Araceli H

[jira] Created: (PIG-670) DIFF contains an invalid expression - possible parser error

DIFF contains an invalid expression - possible parser error --- Key: PIG-670 URL: https://issues.apache.org/jira/browse/PIG-670 Project: Pig Issue Type: Bug Environment: i686

[jira] Created: (PIG-671) typechecker does not throw an error when multiple arguments are passed to COUNT

typechecker does not throw an error when multiple arguments are passed to COUNT --- Key: PIG-671 URL: https://issues.apache.org/jira/browse/PIG-671 Project: Pig Issu

[jira] Created: (PIG-672) bad data output from STREAM operator in trunk (regression from 0.1.1)

bad data output from STREAM operator in trunk (regression from 0.1.1) - Key: PIG-672 URL: https://issues.apache.org/jira/browse/PIG-672 Project: Pig Issue Type: Bug

[jira] Commented: (PIG-672) bad data output from STREAM operator in trunk (regression from 0.1.1)

[ https://issues.apache.org/jira/browse/PIG-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673039#action_12673039 ] Pradeep Kamath commented on PIG-672: Can you try the latest svn trunk - there was an issue

[jira] Created: (PIG-673) several aggregate functions do not check the number of arguments and do not correctly check for a type "bag"

several aggregate functions do not check the number of arguments and do not correctly check for a type "bag" Key: PIG-673 URL: https://issues.apache.org/j

[jira] Updated: (PIG-665) Map key type not correctly set (for use when key is null) when map plan does not have localrearrange

[ https://issues.apache.org/jira/browse/PIG-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-665: --- Attachment: PIG-665.patch > Map key type not correctly set (for use when key is null) when map plan does

[jira] Updated: (PIG-665) Map key type not correctly set (for use when key is null) when map plan does not have localrearrange

[ https://issues.apache.org/jira/browse/PIG-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-665: --- Status: Patch Available (was: Open) The issue as described in the description was that when the map pla

[jira] Created: (PIG-674) Improve errors in Pig parser

Improve errors in Pig parser Key: PIG-674 URL: https://issues.apache.org/jira/browse/PIG-674 Project: Pig Issue Type: Bug Reporter: Araceli Henley Priority: Minor These tests are for Agg

[jira] Created: (PIG-675) Improve backend error messages

Improve backend error messages -- Key: PIG-675 URL: https://issues.apache.org/jira/browse/PIG-675 Project: Pig Issue Type: Bug Environment: i686 i386 GNU/Linux java version "1.6.0_02" Java(TM) SE Runtime

[jira] Commented: (PIG-672) bad data output from STREAM operator in trunk (regression from 0.1.1)

[ https://issues.apache.org/jira/browse/PIG-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673069#action_12673069 ] Daniel Lescohier commented on PIG-672: -- I tested with trunk 743881, and the problem is so

[jira] Updated: (PIG-574) run command for grunt

[ https://issues.apache.org/jira/browse/PIG-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olga Natkovich updated PIG-574: --- Attachment: PIG-574.patch > run command for grunt > - > > Key: PIG-5

[jira] Commented: (PIG-574) run command for grunt

[ https://issues.apache.org/jira/browse/PIG-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673074#action_12673074 ] Olga Natkovich commented on PIG-574: I tested patch and all is good. I have made one small

[jira] Resolved: (PIG-672) bad data output from STREAM operator in trunk (regression from 0.1.1)

[ https://issues.apache.org/jira/browse/PIG-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath resolved PIG-672. Resolution: Invalid Closing the issue based on the last comment. Please reopen if there is still an i

[jira] Updated: (PIG-574) run command for grunt

[ https://issues.apache.org/jira/browse/PIG-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olga Natkovich updated PIG-574: --- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed. Thanks Gunther for c

[jira] Updated: (PIG-590) Error handling phase three

[ https://issues.apache.org/jira/browse/PIG-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Srinivasan updated PIG-590: Attachment: Error_handling_phase3_1.patch Attached patch, implements phase three of the error

[jira] Updated: (PIG-590) Error handling phase three

[ https://issues.apache.org/jira/browse/PIG-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Srinivasan updated PIG-590: Patch Info: [Patch Available] > Error handling phase three > -- > >

[jira] Commented: (PIG-665) Map key type not correctly set (for use when key is null) when map plan does not have localrearrange

[ https://issues.apache.org/jira/browse/PIG-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673079#action_12673079 ] Olga Natkovich commented on PIG-665: +1; please, commit > Map key type not correctly set

[jira] Updated: (PIG-665) Map key type not correctly set (for use when key is null) when map plan does not have localrearrange

[ https://issues.apache.org/jira/browse/PIG-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-665: --- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) Patc

[jira] Commented: (PIG-590) Error handling phase three

[ https://issues.apache.org/jira/browse/PIG-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673086#action_12673086 ] Olga Natkovich commented on PIG-590: I am reviewing this patch. > Error handling phase th

switching to different parser in Pig

Pig Developers, Pig currently uses javacc for parsing pig commands. We have found several shortcomings with using javacc. In particular, (1) Lack of good documentation which makes it hard to and time consuming to learn javacc and make changes to Pig grammar (2) No easy way to customize error ha

[jira] Created: (PIG-676) Diff does not check if the first input is a bag or not

Diff does not check if the first input is a bag or not -- Key: PIG-676 URL: https://issues.apache.org/jira/browse/PIG-676 Project: Pig Issue Type: Bug Environment: i686 i386 GNU/Li

Re: switching to different parser in Pig

In general, it would be really, really nice if it were easy to build abstract Pig syntax trees outside of the normal parser. For instance, I find the fact that pig is not a full scale scripting language incredibly confining. I would love to be able to build a DSL in groovy that let me use groovy

[jira] Commented: (PIG-590) Error handling phase three

[ https://issues.apache.org/jira/browse/PIG-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673117#action_12673117 ] Olga Natkovich commented on PIG-590: I committed the patch. Everything looked really good.

[jira] Updated: (PIG-590) Error handling phase three

[ https://issues.apache.org/jira/browse/PIG-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Srinivasan updated PIG-590: Attachment: Error_handling_phase3_3.patch Patch to fix the issue noted in the previous comment

[jira] Resolved: (PIG-590) Error handling phase three

[ https://issues.apache.org/jira/browse/PIG-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Srinivasan resolved PIG-590. - Resolution: Fixed Hadoop Flags: [Reviewed] All unit tests pass. Patch has been committ

Re: switching to different parser in Pig

This sounds like a great idea ! Would be great if other means of generating ast's for pig was possible. Regards, Mridul Ted Dunning wrote: In general, it would be really, really nice if it were easy to build abstract Pig syntax trees outside of the normal parser. For instance, I find the fact