[jira] Updated: (PIG-818) Explain doesn't handle PODemux properly
[ https://issues.apache.org/jira/browse/PIG-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gunther Hagleitner updated PIG-818: --- Status: Patch Available (was: Open) Explain doesn't handle PODemux properly --- Key: PIG-818 URL: https://issues.apache.org/jira/browse/PIG-818 Project: Pig Issue Type: Bug Reporter: Gunther Hagleitner Assignee: Gunther Hagleitner Attachments: explain.patch The PODemux operator has nested plans but they are not expanded in the -dot version of explain. Also, both split and demux are displayed as clusters of nodes, but it really makes more sense to just show them as multi output operators. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-818) Explain doesn't handle PODemux properly
[ https://issues.apache.org/jira/browse/PIG-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gunther Hagleitner updated PIG-818: --- Attachment: explain.patch Explain doesn't handle PODemux properly --- Key: PIG-818 URL: https://issues.apache.org/jira/browse/PIG-818 Project: Pig Issue Type: Bug Reporter: Gunther Hagleitner Assignee: Gunther Hagleitner Attachments: explain.patch The PODemux operator has nested plans but they are not expanded in the -dot version of explain. Also, both split and demux are displayed as clusters of nodes, but it really makes more sense to just show them as multi output operators. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (PIG-818) Explain doesn't handle PODemux properly
Explain doesn't handle PODemux properly --- Key: PIG-818 URL: https://issues.apache.org/jira/browse/PIG-818 Project: Pig Issue Type: Bug Reporter: Gunther Hagleitner Assignee: Gunther Hagleitner Attachments: explain.patch The PODemux operator has nested plans but they are not expanded in the -dot version of explain. Also, both split and demux are displayed as clusters of nodes, but it really makes more sense to just show them as multi output operators. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-818) Explain doesn't handle PODemux properly
[ https://issues.apache.org/jira/browse/PIG-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12712932#action_12712932 ] Hadoop QA commented on PIG-818: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12409009/explain.patch against trunk revision 08. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no tests are needed for this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/58/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/58/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/58/console This message is automatically generated. Explain doesn't handle PODemux properly --- Key: PIG-818 URL: https://issues.apache.org/jira/browse/PIG-818 Project: Pig Issue Type: Bug Reporter: Gunther Hagleitner Assignee: Gunther Hagleitner Attachments: explain.patch The PODemux operator has nested plans but they are not expanded in the -dot version of explain. Also, both split and demux are displayed as clusters of nodes, but it really makes more sense to just show them as multi output operators. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: UDF with parameters?
You should be able to send the percentile rank that you want to calculate as a udf argument like the way you stated - generate Percentile(90, duration) - here 90 will be an integer constant sent as the first argument to your udf. -Original Message- From: Brian Long [mailto:br...@dotspots.com] Sent: Friday, May 22, 2009 3:38 PM To: pig-dev@hadoop.apache.org Subject: UDF with parameters? Hi, I'm interested in developing a PERCENTILE UDF, e.g. for calculating a median, 99th percentile, 90th percentile, etc. I'd like the UDF to be parametric with respect to the percentile being requested, but I don't see any way to do that, and it seems like I might need to create PERCENTILE_50, PERCENTILE_90, etc type UDFs explicitly, versus being able to do something like GENERATE PERCENTILE(90, duration) I'm new to Pig, so I might be missing the way to do this... is it possible? Thanks, Brian
[jira] Updated: (PIG-804) problem with lineage with double map redirection
[ https://issues.apache.org/jira/browse/PIG-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-804: --- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) Patch was commited on May 13 2009. problem with lineage with double map redirection Key: PIG-804 URL: https://issues.apache.org/jira/browse/PIG-804 Project: Pig Issue Type: Bug Affects Versions: 0.2.1 Reporter: Olga Natkovich Assignee: Pradeep Kamath Fix For: 0.3.0 Attachments: PIG-804.patch v1 = load 'data' as (s,m,l); v2 = foreach v1 GENERATE s#'src_spaceid' AS vspaceid ; v3 = foreach v2 GENERATE (chararray)vspaceid#'foo'; explain v3; The last cast does not have a loader associated with it and as the result the script fails on the backend with the following error: Received a bytearray from the UDF. Cannot determine how to convert the bytearray to string. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-656) Use of eval or any other keyword in the package hierarchy of a UDF causes parse exception
[
https://issues.apache.org/jira/browse/PIG-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713163#action_12713163
]
Santhosh Srinivasan commented on PIG-656:
-
+1 for the patch.
Use of eval or any other keyword in the package hierarchy of a UDF causes
parse exception
-
Key: PIG-656
URL: https://issues.apache.org/jira/browse/PIG-656
Project: Pig
Issue Type: Bug
Components: documentation, grunt
Affects Versions: 0.2.1
Reporter: Viraj Bhat
Assignee: Milind Bhandarkar
Fix For: 0.3.0
Attachments: mywordcount.txt, reserved.patch, TOKENIZE.jar
Consider a Pig script which does something similar to a word count. It uses
the built-in TOKENIZE function, but packages it inside a class hierarchy such
as mypackage.eval
{code}
register TOKENIZE.jar
my_src = LOAD '/user/viraj/mywordcount.txt' USING PigStorage('\t') AS
(mlist: chararray);
modules = FOREACH my_src GENERATE FLATTEN(mypackage.eval.TOKENIZE(mlist));
describe modules;
grouped = GROUP modules BY $0;
describe grouped;
counts = FOREACH grouped GENERATE COUNT(modules), group;
ordered = ORDER counts BY $0;
dump ordered;
{code}
The parser complains:
===
2009-02-05 01:17:29,231 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
1000: Error during parsing. Invalid alias: mypackage in {mlist: chararray}
===
I looked at the following source code at
(src/org/apache/pig/impl/logicalLayer/parser/QueryParser.jjt) and it seems
that : EVAL is a keyword in Pig. Here are some clarifications:
1) Is there documentation on what the EVAL keyword actually is?
2) Is EVAL keyword actually implemented?
Viraj
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-802) PERFORMANCE: not creating bags for ORDER BY
[
https://issues.apache.org/jira/browse/PIG-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713181#action_12713181
]
Pradeep Kamath commented on PIG-802:
Changes look good - still have a comment about the change in MRCompiler.java:
In MRCompiler, does POPackageLite need to be used in the following too:
{noformat}
if (limit!=-1) {
POPackage pkg_c = new POPackage(new
OperatorKey(scope,nig.getNextNodeId(scope)));
...
}
{noformat}
PERFORMANCE: not creating bags for ORDER BY
---
Key: PIG-802
URL: https://issues.apache.org/jira/browse/PIG-802
Project: Pig
Issue Type: Improvement
Affects Versions: 0.2.0
Reporter: Olga Natkovich
Attachments: OrderByOptimization.patch
Order by should be changed to not use POPackage to put all of the tuples in a
bag on the reduce side, as the bag is just immediately flattened. It can
instead work like join does for the last input in the join.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-656) Use of eval or any other keyword in the package hierarchy of a UDF causes parse exception
[
https://issues.apache.org/jira/browse/PIG-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Santhosh Srinivasan updated PIG-656:
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Patch has been committed. Milind, thanks for fixing this issue.
Use of eval or any other keyword in the package hierarchy of a UDF causes
parse exception
-
Key: PIG-656
URL: https://issues.apache.org/jira/browse/PIG-656
Project: Pig
Issue Type: Bug
Components: documentation, grunt
Affects Versions: 0.2.1
Reporter: Viraj Bhat
Assignee: Milind Bhandarkar
Fix For: 0.3.0
Attachments: mywordcount.txt, reserved.patch, TOKENIZE.jar
Consider a Pig script which does something similar to a word count. It uses
the built-in TOKENIZE function, but packages it inside a class hierarchy such
as mypackage.eval
{code}
register TOKENIZE.jar
my_src = LOAD '/user/viraj/mywordcount.txt' USING PigStorage('\t') AS
(mlist: chararray);
modules = FOREACH my_src GENERATE FLATTEN(mypackage.eval.TOKENIZE(mlist));
describe modules;
grouped = GROUP modules BY $0;
describe grouped;
counts = FOREACH grouped GENERATE COUNT(modules), group;
ordered = ORDER counts BY $0;
dump ordered;
{code}
The parser complains:
===
2009-02-05 01:17:29,231 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
1000: Error during parsing. Invalid alias: mypackage in {mlist: chararray}
===
I looked at the following source code at
(src/org/apache/pig/impl/logicalLayer/parser/QueryParser.jjt) and it seems
that : EVAL is a keyword in Pig. Here are some clarifications:
1) Is there documentation on what the EVAL keyword actually is?
2) Is EVAL keyword actually implemented?
Viraj
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Post Summit Developer Offsite
Hadoop Developers, we'd like to let you know about a special developer offsite: http://hadoop-developer-offsite.eventbrite.com/ On the Friday after the summit, we're inviting committers from all Hadoop sub projects to get together for a day of real life camaraderie and a chance to attack some of the issues that are best solved face to face. We'll specifically focus on: * Understanding the major development challenges for the year ahead * Building consensus on the relative priorities of key upcoming features * Improving integration among sub projects * Best practices for packaging and distributing code (making life easier for the ops guys) We also realize that many developers that aren't yet committers will have valuable input, and we'd like to accommodate as many as we have room for. If you aren't a committer, but are actively involved in development, please register as an applicant, and we'll work with the committers on each project to squeeze in as many as we have room for. We know we can't accommodate everyone, but we will do our best, and will of course circulate notes from the meeting. Cheers, Christophe and the Cloudera Team -- get hadoop: cloudera.com/hadoop online training: cloudera.com/hadoop-training blog: cloudera.com/blog twitter: twitter.com/cloudera
[jira] Created: (PIG-819) run -param -param; is a valid grunt command
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Status: Patch Available (was: Open)
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Attachment: invalidparam.patch
This patch makes the -arguments to pig commands actually contain an argument
when needed after them, rather than accepting commands such as run -param
-param.
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Attachment: (was: invalidparam.patch)
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Status: Open (was: Patch Available)
cancelling patch, so as to fix the testcase.
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PIG-779) Warning from javacc
[ https://issues.apache.org/jira/browse/PIG-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milind Bhandarkar resolved PIG-779. --- Resolution: Duplicate Fix for PIG-819 fixes this. Warning from javacc --- Key: PIG-779 URL: https://issues.apache.org/jira/browse/PIG-779 Project: Pig Issue Type: Improvement Reporter: Gunther Hagleitner This warning needs fixing: Reading from file .../src/org/apache/pig/tools/pigscript/parser/PigScriptParser.jj . . . [javacc] Warning: Choice conflict in (...)* construct at line 560, column 9. [javacc] Expansion nested within construct and expansion following construct [javacc] have common prefixes, one of which is: -param [javacc] Consider using a lookahead of 2 or more for nested expansion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-802) PERFORMANCE: not creating bags for ORDER BY
[ https://issues.apache.org/jira/browse/PIG-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Setty updated PIG-802: - Attachment: OrderByOptimization.patch Latest patch with the correction for limit clause. PERFORMANCE: not creating bags for ORDER BY --- Key: PIG-802 URL: https://issues.apache.org/jira/browse/PIG-802 Project: Pig Issue Type: Improvement Affects Versions: 0.2.0 Reporter: Olga Natkovich Attachments: OrderByOptimization.patch Order by should be changed to not use POPackage to put all of the tuples in a bag on the reduce side, as the bag is just immediately flattened. It can instead work like join does for the last input in the join. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Attachment: invalidparam.patch
Attaching fixed patch with testcase.
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Status: Patch Available (was: Open)
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Attachment: (was: invalidparam.patch)
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Status: Open (was: Patch Available)
somehow uploaded the old patch again :-(
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Build failed in Hudson: Pig-Patch-minerva.apache.org #59
See http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/59/changes Changes: [sms] PIG-656: Use of eval or any other keyword in the package hierarchy of a UDF causes parse exception (milindb via sms) -- started Building remotely on minerva.apache.org (Ubuntu) Updating http://svn.apache.org/repos/asf/hadoop/pig/trunk U test/org/apache/pig/test/TestLogicalPlanBuilder.java U CHANGES.txt U src/org/apache/pig/impl/logicalLayer/parser/QueryParser.jjt Fetching 'http://svn.apache.org/repos/asf/hadoop/core/nightly/test-patch' at -1 into 'http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/ws/trunk/test/bin' At revision 778914 At revision 778914 no change for http://svn.apache.org/repos/asf/hadoop/core/nightly/test-patch since the previous build [Pig-Patch-minerva.apache.org] $ /bin/bash /tmp/hudson6829945214878368465.sh /home/hudson/tools/java/latest1.6/bin/java Buildfile: build.xml check-for-findbugs: findbugs.check: java5.check: forrest.check: hudson-test-patch: [exec] [exec] [exec] == [exec] == [exec] Testing patch for PIG-819. [exec] == [exec] == [exec] [exec] [exec] Reverted 'src/org/apache/pig/backend/hadoop/executionengine/mapReduceLayer/plans/DotMRPrinter.java' [exec] Reverted 'src/org/apache/pig/backend/hadoop/executionengine/physicalLayer/plans/DotPOPrinter.java' [exec] Reverted 'src/org/apache/pig/backend/hadoop/executionengine/physicalLayer/plans/PlanPrinter.java' [exec] Reverted 'src/org/apache/pig/impl/logicalLayer/DotLOPrinter.java' [exec] Reverted 'src/org/apache/pig/impl/plan/PlanDumper.java' [exec] Reverted 'src/org/apache/pig/impl/plan/DotPlanDumper.java' [exec] [exec] Fetching external item into 'test/bin' [exec] Atest/bin/test-patch.sh [exec] Updated external to revision 778914. [exec] [exec] Updated to revision 778914. [exec] PIG-819 is not Patch Available. Exiting. [exec] % Total% Received % Xferd Average Speed TimeTime Time Current [exec] Dload Upload Total Spent Left Speed [exec] [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] [exec] 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 BUILD SUCCESSFUL Total time: 9 seconds ERROR: No artifacts found that match the file pattern trunk/build/test/findbugs/newPatchFindbugsWarnings.html,trunk/patchprocess/*Warnings.txt. Configuration error? ERROR: 'trunk/build/test/findbugs/newPatchFindbugsWarnings.html' doesn't match anything: 'trunk' exists but not 'trunk/build/test/findbugs/newPatchFindbugsWarnings.html' Recording test results Description found: PIG-819
Build failed in Hudson: Pig-Patch-minerva.apache.org #60
See http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/60/ -- started Building remotely on minerva.apache.org (Ubuntu) Updating http://svn.apache.org/repos/asf/hadoop/pig/trunk Fetching 'http://svn.apache.org/repos/asf/hadoop/core/nightly/test-patch' at -1 into 'http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/ws/trunk/test/bin' At revision 778915 At revision 778915 no change for http://svn.apache.org/repos/asf/hadoop/pig/trunk since the previous build no change for http://svn.apache.org/repos/asf/hadoop/core/nightly/test-patch since the previous build [Pig-Patch-minerva.apache.org] $ /bin/bash /tmp/hudson3172373432727401567.sh /home/hudson/tools/java/latest1.6/bin/java Buildfile: build.xml check-for-findbugs: findbugs.check: java5.check: forrest.check: hudson-test-patch: [exec] [exec] [exec] == [exec] == [exec] Testing patch for PIG-819. [exec] == [exec] == [exec] [exec] [exec] [exec] Fetching external item into 'test/bin' [exec] Atest/bin/test-patch.sh [exec] Updated external to revision 778915. [exec] [exec] Updated to revision 778915. [exec] PIG-819 is not Patch Available. Exiting. [exec] % Total% Received % Xferd Average Speed TimeTime Time Current [exec] Dload Upload Total Spent Left Speed [exec] [exec] 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 2 seconds ERROR: No artifacts found that match the file pattern trunk/build/test/findbugs/newPatchFindbugsWarnings.html,trunk/patchprocess/*Warnings.txt. Configuration error? ERROR: 'trunk/build/test/findbugs/newPatchFindbugsWarnings.html' doesn't match anything: 'trunk' exists but not 'trunk/build/test/findbugs/newPatchFindbugsWarnings.html' Recording test results Description found: PIG-819
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Status: Patch Available (was: Open)
yes, it is the right patch :-)
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated PIG-819:
--
Attachment: invalidparam.patch
Hoping to upload the right patch this time :-)
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-819) run -param -param; is a valid grunt command
[
https://issues.apache.org/jira/browse/PIG-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713343#action_12713343
]
Hadoop QA commented on PIG-819:
---
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12409094/invalidparam.patch
against trunk revision 778872.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/61/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/61/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/61/console
This message is automatically generated.
run -param -param; is a valid grunt command
---
Key: PIG-819
URL: https://issues.apache.org/jira/browse/PIG-819
Project: Pig
Issue Type: Bug
Components: grunt
Affects Versions: 0.3.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Milind Bhandarkar
Attachments: invalidparam.patch
By mistake, I typed
{code}
run -param -param;
{code}
in grunt. And was surprised to find it to be a valid grunt command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hudson build is back to normal: Pig-Patch-minerva.apache.org #61
See http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/61/
[jira] Created: (PIG-820) PERFORMANCE: The RandomSampleLoader should be changed to allow it subsume another loader
PERFORMANCE: The RandomSampleLoader should be changed to allow it subsume
another loader
-
Key: PIG-820
URL: https://issues.apache.org/jira/browse/PIG-820
Project: Pig
Issue Type: Improvement
Components: impl
Affects Versions: 0.3.0
Reporter: Alan Gates
Assignee: Alan Gates
Currently a sampling job requires that data already be stored in BinaryStorage
format, since RandomSampleLoader extends BinaryStorage. For order by this
has mostly been acceptable, because users tend to use order by at the end of
their script where other MR jobs have already operated on the data and thus it
is already being stored in BinaryStorage. For pig scripts that just did an
order by, an entire MR job is required to read the data and write it out
in BinaryStorage format.
As we begin work on join algorithms that will require sampling, this
requirement to read the entire input and write it back out will not be
acceptable.
Join is often the first operation of a script, and thus is much more likely to
trigger this useless up front translation job.
Instead RandomSampleLoader can be changed to subsume an existing loader, using
the user specified loader to read the tuples while handling the skipping
between tuples itself. This will require the subsumed loader to implement a
Samplable Interface, that will look something like:
{code}
public interface SamplableLoader extends LoadFunc {
/**
* Skip ahead in the input stream.
* @param n number of bytes to skip
* @return number of bytes actually skipped. The return semantics are
* exactly the same as {...@link java.io.InpuStream#skip(long)}
*/
public long skip(long n) throws IOException;
/**
* Get the current position in the stream.
* @return position in the stream.
*/
public long getPosition() throws IOException;
}
{code}
The MRCompiler would then check if the loader being used to load data
implemented the SamplableLoader interface. If so, rather than create an
initial MR
job to do the translation it would create the sampling job, having
RandomSampleLoader use the user specified loader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-701) Implement IVY for resolving pig dependencies
[ https://issues.apache.org/jira/browse/PIG-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated PIG-701: --- Resolution: Fixed Fix Version/s: 0.3.0 Status: Resolved (was: Patch Available) Implement IVY for resolving pig dependencies - Key: PIG-701 URL: https://issues.apache.org/jira/browse/PIG-701 Project: Pig Issue Type: New Feature Components: build Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan Fix For: 0.3.0 Attachments: lib_rm.sh, PIG-701.patch, PIG-701.patch, PIG-701.patch, PIG-701.patch pig libraries to be resolved using IVY from the centralized maven repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
