[jira] [Updated] (PIG-3150) e2e Scripting_5 fails in trunk
[
https://issues.apache.org/jira/browse/PIG-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johnny Zhang updated PIG-3150:
--
Status: Patch Available (was: Open)
I fix the test by define the schema of the result in the jython script. The
test pass for me
> e2e Scripting_5 fails in trunk
> --
>
> Key: PIG-3150
> URL: https://issues.apache.org/jira/browse/PIG-3150
> Project: Pig
> Issue Type: Bug
> Components: e2e harness
>Affects Versions: 0.12
>Reporter: Cheolsoo Park
>Assignee: Johnny Zhang
> Fix For: 0.12
>
> Attachments: PIG-3150.patch.txt
>
>
> To reproduce the error, please do:
> {code}
> ant -Dhadoopversion=20 -Dharness.old.pig=`pwd`
> -Dharness.cluster.conf=/etc/hadoop/conf/
> -Dharness.cluster.bin=/usr/lib/hadoop/bin/hadoop test-e2e -Dtests.to.run="-t
> Scripting_5"
> {code}
> PIG-3082 introduced a new Front-end exception, and that makes e2e Scripting_5
> fail with the following error:
> {code}
> 2013-01-30 15:08:41,340 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
> 1200: Pig script failed to parse:
> ./out/pigtest/cheolsoo/cheolsoo-1359586527-nightly.conf-Scripting/Scripting_5.pig,
> line 4, column 4> pig script failed to validate:
> org.apache.pig.impl.logicalLayer.FrontendException: ERROR 0: Given UDF
> returns an improper Schema. Schema should only contain one field of a Tuple,
> Bag, or a single type. Returns: {outm: map[],outt: (name: chararray,age:
> int,gpa: double),outb: {t: (name: chararray,age: int,gpa: double)}}
> {code}
> And here is the stack trace:
> {code}
> Caused by: org.apache.pig.impl.logicalLayer.FrontendException: ERROR 0: Given
> UDF returns an improper Schema. Schema should only contain one field of a
> Tuple, Bag, or a single type. Returns: {outm: map[],outt: (name:
> chararray,age: int,gpa: double),outb: {t: (name: chararray,age: int,gpa:
> double)}}
> at
> org.apache.pig.newplan.logical.expression.UserFuncExpression.getFieldSchema(UserFuncExpression.java:206)
> at
> org.apache.pig.newplan.logical.optimizer.FieldSchemaResetter.execute(SchemaResetter.java:264)
> at
> org.apache.pig.newplan.logical.expression.AllSameExpressionVisitor.visit(AllSameExpressionVisitor.java:143)
> at
> org.apache.pig.newplan.logical.expression.UserFuncExpression.accept(UserFuncExpression.java:88)
> at
> org.apache.pig.newplan.ReverseDependencyOrderWalker.walk(ReverseDependencyOrderWalker.java:70)
> at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:52)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visitAll(SchemaResetter.java:67)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visit(SchemaResetter.java:122)
> at
> org.apache.pig.newplan.logical.relational.LOGenerate.accept(LOGenerate.java:240)
> at
> org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visit(SchemaResetter.java:114)
> at
> org.apache.pig.newplan.logical.relational.LOForEach.accept(LOForEach.java:76)
> at
> org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
> at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:52)
> at
> org.apache.pig.parser.LogicalPlanBuilder.expandAndResetVisitor(LogicalPlanBuilder.java:402)
> ... 22 more
> {code}
--
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
[jira] [Updated] (PIG-3150) e2e Scripting_5 fails in trunk
[
https://issues.apache.org/jira/browse/PIG-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johnny Zhang updated PIG-3150:
--
Attachment: PIG-3150.patch.txt
> e2e Scripting_5 fails in trunk
> --
>
> Key: PIG-3150
> URL: https://issues.apache.org/jira/browse/PIG-3150
> Project: Pig
> Issue Type: Bug
> Components: e2e harness
>Affects Versions: 0.12
>Reporter: Cheolsoo Park
>Assignee: Johnny Zhang
> Fix For: 0.12
>
> Attachments: PIG-3150.patch.txt
>
>
> To reproduce the error, please do:
> {code}
> ant -Dhadoopversion=20 -Dharness.old.pig=`pwd`
> -Dharness.cluster.conf=/etc/hadoop/conf/
> -Dharness.cluster.bin=/usr/lib/hadoop/bin/hadoop test-e2e -Dtests.to.run="-t
> Scripting_5"
> {code}
> PIG-3082 introduced a new Front-end exception, and that makes e2e Scripting_5
> fail with the following error:
> {code}
> 2013-01-30 15:08:41,340 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
> 1200: Pig script failed to parse:
> ./out/pigtest/cheolsoo/cheolsoo-1359586527-nightly.conf-Scripting/Scripting_5.pig,
> line 4, column 4> pig script failed to validate:
> org.apache.pig.impl.logicalLayer.FrontendException: ERROR 0: Given UDF
> returns an improper Schema. Schema should only contain one field of a Tuple,
> Bag, or a single type. Returns: {outm: map[],outt: (name: chararray,age:
> int,gpa: double),outb: {t: (name: chararray,age: int,gpa: double)}}
> {code}
> And here is the stack trace:
> {code}
> Caused by: org.apache.pig.impl.logicalLayer.FrontendException: ERROR 0: Given
> UDF returns an improper Schema. Schema should only contain one field of a
> Tuple, Bag, or a single type. Returns: {outm: map[],outt: (name:
> chararray,age: int,gpa: double),outb: {t: (name: chararray,age: int,gpa:
> double)}}
> at
> org.apache.pig.newplan.logical.expression.UserFuncExpression.getFieldSchema(UserFuncExpression.java:206)
> at
> org.apache.pig.newplan.logical.optimizer.FieldSchemaResetter.execute(SchemaResetter.java:264)
> at
> org.apache.pig.newplan.logical.expression.AllSameExpressionVisitor.visit(AllSameExpressionVisitor.java:143)
> at
> org.apache.pig.newplan.logical.expression.UserFuncExpression.accept(UserFuncExpression.java:88)
> at
> org.apache.pig.newplan.ReverseDependencyOrderWalker.walk(ReverseDependencyOrderWalker.java:70)
> at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:52)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visitAll(SchemaResetter.java:67)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visit(SchemaResetter.java:122)
> at
> org.apache.pig.newplan.logical.relational.LOGenerate.accept(LOGenerate.java:240)
> at
> org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visit(SchemaResetter.java:114)
> at
> org.apache.pig.newplan.logical.relational.LOForEach.accept(LOForEach.java:76)
> at
> org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
> at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:52)
> at
> org.apache.pig.parser.LogicalPlanBuilder.expandAndResetVisitor(LogicalPlanBuilder.java:402)
> ... 22 more
> {code}
--
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
[jira] [Updated] (PIG-3189) Remove ivy/pig.pom and improve build mvn targets
[
https://issues.apache.org/jira/browse/PIG-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Graham updated PIG-3189:
-
Status: Patch Available (was: Open)
> Remove ivy/pig.pom and improve build mvn targets
>
>
> Key: PIG-3189
> URL: https://issues.apache.org/jira/browse/PIG-3189
> Project: Pig
> Issue Type: Bug
>Reporter: Bill Graham
>Assignee: Bill Graham
> Fix For: 0.12
>
> Attachments: PIG-3189.1.patch
>
>
> {{ivy/pig.pom}} SVN seems to no longer be used. At build time ({{ant
> set-version}} via {{ant mvn-deploy}}) {{ivy/pig.pom}} is generated from
> {{ivy/pig-template.xml}}. We should remove {{ivy/pig.pom}} from SVN.
> It would also be good to decouple building the maven artifacts from
> publishing them, since those two tasks might be done on different hosts.
--
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
[jira] [Updated] (PIG-3189) Remove ivy/pig.pom and improve build mvn targets
[
https://issues.apache.org/jira/browse/PIG-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Graham updated PIG-3189:
-
Attachment: PIG-3189.1.patch
Attaching a patch. Patch doesn't include deletion of {{ivy/pig.pom}} since I
can't seem to get that reflected once the file is deleted.
> Remove ivy/pig.pom and improve build mvn targets
>
>
> Key: PIG-3189
> URL: https://issues.apache.org/jira/browse/PIG-3189
> Project: Pig
> Issue Type: Bug
>Reporter: Bill Graham
>Assignee: Bill Graham
> Fix For: 0.12
>
> Attachments: PIG-3189.1.patch
>
>
> {{ivy/pig.pom}} SVN seems to no longer be used. At build time ({{ant
> set-version}} via {{ant mvn-deploy}}) {{ivy/pig.pom}} is generated from
> {{ivy/pig-template.xml}}. We should remove {{ivy/pig.pom}} from SVN.
> It would also be good to decouple building the maven artifacts from
> publishing them, since those two tasks might be done on different hosts.
--
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
[jira] [Created] (PIG-3189) Remove ivy/pig.pom and improve build mvn targets
Bill Graham created PIG-3189:
Summary: Remove ivy/pig.pom and improve build mvn targets
Key: PIG-3189
URL: https://issues.apache.org/jira/browse/PIG-3189
Project: Pig
Issue Type: Bug
Reporter: Bill Graham
Assignee: Bill Graham
Fix For: 0.12
{{ivy/pig.pom}} SVN seems to no longer be used. At build time ({{ant
set-version}} via {{ant mvn-deploy}}) {{ivy/pig.pom}} is generated from
{{ivy/pig-template.xml}}. We should remove {{ivy/pig.pom}} from SVN.
It would also be good to decouple building the maven artifacts from publishing
them, since those two tasks might be done on different hosts.
--
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
[jira] Subscription: PIG patch available
Issue Subscription Filter: PIG patch available (30 issues) Subscriber: pigdaily Key Summary PIG-3185Pig release lacks UDF for Initcap function https://issues.apache.org/jira/browse/PIG-3185 PIG-3184Pig release lacks UDF for functions rtrim and repeat https://issues.apache.org/jira/browse/PIG-3184 PIG-3182Pig currently lacks function to trim the whitespace only on the left hand side https://issues.apache.org/jira/browse/PIG-3182 PIG-3174Remove rpm and deb artifacts from build.xml https://issues.apache.org/jira/browse/PIG-3174 PIG-3169Remove temporary files that are not needed https://issues.apache.org/jira/browse/PIG-3169 PIG-3167Job stats are printed incorrectly for map-only jobs https://issues.apache.org/jira/browse/PIG-3167 PIG-3166Update eclipse .classpath according to ivy library.properties https://issues.apache.org/jira/browse/PIG-3166 PIG-3164Pig current releases lack a UDF endsWith.This UDF tests if a given string ends with the specified suffix. https://issues.apache.org/jira/browse/PIG-3164 PIG-3162PigTest.assertOutput doesn't allow non-default delimiter https://issues.apache.org/jira/browse/PIG-3162 PIG-3158Errors in the document "Control Structures" https://issues.apache.org/jira/browse/PIG-3158 PIG-3153TestScriptUDF.testJavascriptExampleScript fails in trunk https://issues.apache.org/jira/browse/PIG-3153 PIG-3142Fixed-width load and store functions for the Piggybank https://issues.apache.org/jira/browse/PIG-3142 PIG-3136Introduce a syntax making declared aliases optional https://issues.apache.org/jira/browse/PIG-3136 PIG-3123Simplify Logical Plans By Removing Unneccessary Identity Projections https://issues.apache.org/jira/browse/PIG-3123 PIG-3114Duplicated macro name error when using pigunit https://issues.apache.org/jira/browse/PIG-3114 PIG-3105Fix TestJobSubmission unit test failure. https://issues.apache.org/jira/browse/PIG-3105 PIG-3098Add another test for the self join case https://issues.apache.org/jira/browse/PIG-3098 PIG-3088Add a builtin udf which removes prefixes https://issues.apache.org/jira/browse/PIG-3088 PIG-3069Native Windows Compatibility for Pig E2E Tests and Harness https://issues.apache.org/jira/browse/PIG-3069 PIG-3028testGrunt dev test needs some command filters to run correctly without cygwin https://issues.apache.org/jira/browse/PIG-3028 PIG-3027pigTest unit test needs a newline filter for comparisons of golden multi-line https://issues.apache.org/jira/browse/PIG-3027 PIG-3026Pig checked-in baseline comparisons need a pre-filter to address OS-specific newline differences https://issues.apache.org/jira/browse/PIG-3026 PIG-3024TestEmptyInputDir unit test - hadoop version detection logic is brittle https://issues.apache.org/jira/browse/PIG-3024 PIG-3015Rewrite of AvroStorage https://issues.apache.org/jira/browse/PIG-3015 PIG-3010Allow UDF's to flatten themselves https://issues.apache.org/jira/browse/PIG-3010 PIG-2959Add a pig.cmd for Pig to run under Windows https://issues.apache.org/jira/browse/PIG-2959 PIG-2955 Fix bunch of Pig e2e tests on Windows https://issues.apache.org/jira/browse/PIG-2955 PIG-2880Pig current releases lack a UDF charAt.This UDF returns the char value at the specified index. https://issues.apache.org/jira/browse/PIG-2880 PIG-1914Support load/store JSON data in Pig https://issues.apache.org/jira/browse/PIG-1914 PIG-1151Date Conversion + Arithmetic UDFs https://issues.apache.org/jira/browse/PIG-1151 You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13225&filterId=12322384
[jira] [Commented] (PIG-3174) Remove rpm and deb artifacts from build.xml
[ https://issues.apache.org/jira/browse/PIG-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579643#comment-13579643 ] Bill Graham commented on PIG-3174: -- I'll take a look at the patch, but what are your thoughts on documentation or more generally, how we should point people to Bigtop for distros? > Remove rpm and deb artifacts from build.xml > --- > > Key: PIG-3174 > URL: https://issues.apache.org/jira/browse/PIG-3174 > Project: Pig > Issue Type: Task > Components: build >Affects Versions: 0.12 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 0.12 > > Attachments: PIG-3174.2.patch, PIG-3174.patch > > > I propose that we remove the targets to build rpms and debs from build.xml > and consequently quit publishing them as part of our releases. Bigtop > publishes these packages now. And building them takes infrastructure that > not every committer/PMC member has. -- 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
[jira] [Updated] (PIG-3174) Remove rpm and deb artifacts from build.xml
[ https://issues.apache.org/jira/browse/PIG-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-3174: Status: Patch Available (was: Open) > Remove rpm and deb artifacts from build.xml > --- > > Key: PIG-3174 > URL: https://issues.apache.org/jira/browse/PIG-3174 > Project: Pig > Issue Type: Task > Components: build >Affects Versions: 0.12 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 0.12 > > Attachments: PIG-3174.2.patch, PIG-3174.patch > > > I propose that we remove the targets to build rpms and debs from build.xml > and consequently quit publishing them as part of our releases. Bigtop > publishes these packages now. And building them takes infrastructure that > not every committer/PMC member has. -- 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
[jira] [Updated] (PIG-3174) Remove rpm and deb artifacts from build.xml
[ https://issues.apache.org/jira/browse/PIG-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-3174: Attachment: PIG-3174.2.patch A new version of the patch that removes the files for rpm and deb under src/packages > Remove rpm and deb artifacts from build.xml > --- > > Key: PIG-3174 > URL: https://issues.apache.org/jira/browse/PIG-3174 > Project: Pig > Issue Type: Task > Components: build >Affects Versions: 0.12 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 0.12 > > Attachments: PIG-3174.2.patch, PIG-3174.patch > > > I propose that we remove the targets to build rpms and debs from build.xml > and consequently quit publishing them as part of our releases. Bigtop > publishes these packages now. And building them takes infrastructure that > not every committer/PMC member has. -- 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
[jira] [Commented] (PIG-2553) Pig shouldn't allow attempts to write multiple relations into same directory
[ https://issues.apache.org/jira/browse/PIG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579552#comment-13579552 ] Cheolsoo Park commented on PIG-2553: [~prkommireddi], sorry for the delay. I am looking at it now. > Pig shouldn't allow attempts to write multiple relations into same directory > > > Key: PIG-2553 > URL: https://issues.apache.org/jira/browse/PIG-2553 > Project: Pig > Issue Type: Improvement >Reporter: Dmitriy V. Ryaboy >Assignee: Prashant Kommireddi > Attachments: PIG-2553_1.patch, PIG-2553_2.patch, PIG-2553.patch > > > We've seen multiple occasions where users accidentally try to store 2 or more > different relations to the same destination directory. Currently, this passes > the Pig planner and fails on MR side due to concurrent attempts to create the > same part file on the reducer. This is extremely confusing to the user, and > hard to debug. > We should instead fail their scripts before they are even submitted, since we > can identify the erroneous condition from the beginning. -- 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
[jira] [Commented] (PIG-2553) Pig shouldn't allow attempts to write multiple relations into same directory
[ https://issues.apache.org/jira/browse/PIG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579579#comment-13579579 ] Cheolsoo Park commented on PIG-2553: Looks good to me. I am running full unit test to make sure nothing is broken. > Pig shouldn't allow attempts to write multiple relations into same directory > > > Key: PIG-2553 > URL: https://issues.apache.org/jira/browse/PIG-2553 > Project: Pig > Issue Type: Improvement >Reporter: Dmitriy V. Ryaboy >Assignee: Prashant Kommireddi > Attachments: PIG-2553_1.patch, PIG-2553_2.patch, PIG-2553.patch > > > We've seen multiple occasions where users accidentally try to store 2 or more > different relations to the same destination directory. Currently, this passes > the Pig planner and fails on MR side due to concurrent attempts to create the > same part file on the reducer. This is extremely confusing to the user, and > hard to debug. > We should instead fail their scripts before they are even submitted, since we > can identify the erroneous condition from the beginning. -- 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
[jira] [Commented] (PIG-2337) Provide UDF with input schema
[
https://issues.apache.org/jira/browse/PIG-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579532#comment-13579532
]
Dmitriy V. Ryaboy commented on PIG-2337:
Is anything preventing you from calling {code}new ResourceSchema(Schema
pigSchema){code}?
> Provide UDF with input schema
> -
>
> Key: PIG-2337
> URL: https://issues.apache.org/jira/browse/PIG-2337
> Project: Pig
> Issue Type: Improvement
>Reporter: Olga Natkovich
>Assignee: xuting zhao
> Fix For: 0.11
>
> Attachments: PIG-2337-2.patch, PIG-2337-3.patch, PIG-2337-4.patch,
> PIG-2337-5.patch, PIG-2337.patch
>
>
> We have several requests to make input schema available to the UDF for
> inspection.
--
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
[jira] [Commented] (PIG-2337) Provide UDF with input schema
[ https://issues.apache.org/jira/browse/PIG-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579504#comment-13579504 ] Russell Jurney commented on PIG-2337: - I am looking at JsonStorage in the process of writing ToJson as a builtin, and it uses ResourceSchema, which are serializable. The implementation uses features like: field.getName(), schema.getFields(), field.getSchema() - can you tell me the schema equivalents? > Provide UDF with input schema > - > > Key: PIG-2337 > URL: https://issues.apache.org/jira/browse/PIG-2337 > Project: Pig > Issue Type: Improvement >Reporter: Olga Natkovich >Assignee: xuting zhao > Fix For: 0.11 > > Attachments: PIG-2337-2.patch, PIG-2337-3.patch, PIG-2337-4.patch, > PIG-2337-5.patch, PIG-2337.patch > > > We have several requests to make input schema available to the UDF for > inspection. -- 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
[jira] [Updated] (PIG-3150) e2e Scripting_5 fails in trunk
[
https://issues.apache.org/jira/browse/PIG-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johnny Zhang updated PIG-3150:
--
Attachment: (was: PIG-3150.patch.txt)
> e2e Scripting_5 fails in trunk
> --
>
> Key: PIG-3150
> URL: https://issues.apache.org/jira/browse/PIG-3150
> Project: Pig
> Issue Type: Bug
> Components: e2e harness
>Affects Versions: 0.12
>Reporter: Cheolsoo Park
>Assignee: Johnny Zhang
> Fix For: 0.12
>
>
> To reproduce the error, please do:
> {code}
> ant -Dhadoopversion=20 -Dharness.old.pig=`pwd`
> -Dharness.cluster.conf=/etc/hadoop/conf/
> -Dharness.cluster.bin=/usr/lib/hadoop/bin/hadoop test-e2e -Dtests.to.run="-t
> Scripting_5"
> {code}
> PIG-3082 introduced a new Front-end exception, and that makes e2e Scripting_5
> fail with the following error:
> {code}
> 2013-01-30 15:08:41,340 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
> 1200: Pig script failed to parse:
> ./out/pigtest/cheolsoo/cheolsoo-1359586527-nightly.conf-Scripting/Scripting_5.pig,
> line 4, column 4> pig script failed to validate:
> org.apache.pig.impl.logicalLayer.FrontendException: ERROR 0: Given UDF
> returns an improper Schema. Schema should only contain one field of a Tuple,
> Bag, or a single type. Returns: {outm: map[],outt: (name: chararray,age:
> int,gpa: double),outb: {t: (name: chararray,age: int,gpa: double)}}
> {code}
> And here is the stack trace:
> {code}
> Caused by: org.apache.pig.impl.logicalLayer.FrontendException: ERROR 0: Given
> UDF returns an improper Schema. Schema should only contain one field of a
> Tuple, Bag, or a single type. Returns: {outm: map[],outt: (name:
> chararray,age: int,gpa: double),outb: {t: (name: chararray,age: int,gpa:
> double)}}
> at
> org.apache.pig.newplan.logical.expression.UserFuncExpression.getFieldSchema(UserFuncExpression.java:206)
> at
> org.apache.pig.newplan.logical.optimizer.FieldSchemaResetter.execute(SchemaResetter.java:264)
> at
> org.apache.pig.newplan.logical.expression.AllSameExpressionVisitor.visit(AllSameExpressionVisitor.java:143)
> at
> org.apache.pig.newplan.logical.expression.UserFuncExpression.accept(UserFuncExpression.java:88)
> at
> org.apache.pig.newplan.ReverseDependencyOrderWalker.walk(ReverseDependencyOrderWalker.java:70)
> at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:52)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visitAll(SchemaResetter.java:67)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visit(SchemaResetter.java:122)
> at
> org.apache.pig.newplan.logical.relational.LOGenerate.accept(LOGenerate.java:240)
> at
> org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
> at
> org.apache.pig.newplan.logical.optimizer.SchemaResetter.visit(SchemaResetter.java:114)
> at
> org.apache.pig.newplan.logical.relational.LOForEach.accept(LOForEach.java:76)
> at
> org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
> at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:52)
> at
> org.apache.pig.parser.LogicalPlanBuilder.expandAndResetVisitor(LogicalPlanBuilder.java:402)
> ... 22 more
> {code}
--
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
[jira] [Updated] (PIG-3174) Remove rpm and deb artifacts from build.xml
[ https://issues.apache.org/jira/browse/PIG-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-3174: Status: Open (was: Patch Available) Good catch, I'll deal with the now unnecessary files and upload a new patch. > Remove rpm and deb artifacts from build.xml > --- > > Key: PIG-3174 > URL: https://issues.apache.org/jira/browse/PIG-3174 > Project: Pig > Issue Type: Task > Components: build >Affects Versions: 0.12 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 0.12 > > Attachments: PIG-3174.patch > > > I propose that we remove the targets to build rpms and debs from build.xml > and consequently quit publishing them as part of our releases. Bigtop > publishes these packages now. And building them takes infrastructure that > not every committer/PMC member has. -- 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
[jira] [Created] (PIG-3188) pig.script.submitted.timestamp not always consistent for jobs launched in a given script
Bill Graham created PIG-3188:
Summary: pig.script.submitted.timestamp not always consistent for
jobs launched in a given script
Key: PIG-3188
URL: https://issues.apache.org/jira/browse/PIG-3188
Project: Pig
Issue Type: Bug
Reporter: Bill Graham
Assignee: Bill Graham
Fix For: 0.12
{{pig.script.submitted.timestamp}} is set in {{MapReduceLauncher.launchPig()}}
when the a MR plan is launched. Some scripts (i.e. those with an exec in the
middle) will cause multiple plans to be launched. In these case jobs launched
from the same script can have different {{pig.script.submitted.timestamp}}
values, which is a bug.
--
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
[jira] [Assigned] (PIG-3187) Add -tagFile and -tagPath options to AvroStorage
[ https://issues.apache.org/jira/browse/PIG-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho reassigned PIG-3187: --- Assignee: Jarek Jarcec Cecho > Add -tagFile and -tagPath options to AvroStorage > > > Key: PIG-3187 > URL: https://issues.apache.org/jira/browse/PIG-3187 > Project: Pig > Issue Type: Improvement >Affects Versions: 0.11 >Reporter: Cheolsoo Park >Assignee: Jarek Jarcec Cecho >Priority: Minor > > PigStorage already supports these options, and it can be useful in > AvroStorage as well in particular when we want to filter records by filenames. -- 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
[jira] [Created] (PIG-3187) Add -tagFile and -tagPath options to AvroStorage
Cheolsoo Park created PIG-3187: -- Summary: Add -tagFile and -tagPath options to AvroStorage Key: PIG-3187 URL: https://issues.apache.org/jira/browse/PIG-3187 Project: Pig Issue Type: Improvement Affects Versions: 0.11 Reporter: Cheolsoo Park Priority: Minor PigStorage already supports these options, and it can be useful in AvroStorage as well in particular when we want to filter records by filenames. -- 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
