[
https://issues.apache.org/jira/browse/PIG-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-200:
---
Attachment: pigmix2.patch
pigmix2.patch include all queries for PigMix2. It contains original 12 PigMix
queries
[
https://issues.apache.org/jira/browse/PIG-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879209#action_12879209
]
Hadoop QA commented on PIG-1451:
-1 overall. Here are the results of testing the latest atta
[
https://issues.apache.org/jira/browse/PIG-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879201#action_12879201
]
Julien Le Dem commented on PIG-928:
---
I like the suggestion. However I would prefer not to us
[
https://issues.apache.org/jira/browse/PIG-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879181#action_12879181
]
Alan Gates commented on PIG-928:
I propose the following syntax for register:
{code}
REGISTER
[
https://issues.apache.org/jira/browse/PIG-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879066#action_12879066
]
Gaurav Jain commented on PIG-1451:
--
+1
> [zebra] change the build.test property in build t
Might be ok if we artificially limit this to only work with algebraic
functions.
On Tue, Jun 15, 2010 at 9:14 AM, Alan Gates wrote:
> There have been several requests for this. I'm not a fan of it, because it
> makes it too easy to forget that you're forcing a single reducer MR job to
> accompl
[
https://issues.apache.org/jira/browse/PIG-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Zhou updated PIG-1451:
--
Attachment: PIG-1451.patch
> [zebra] change the build.test property in build to test.build.dir to be in
> consis
[
https://issues.apache.org/jira/browse/PIG-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Zhou updated PIG-1451:
--
Status: Patch Available (was: Open)
> [zebra] change the build.test property in build to test.build.dir to be in
[zebra] change the build.test property in build to test.build.dir to be in
consistent with PIG
--
Key: PIG-1451
URL: https://issues.apache.org/jira/browse/PIG-1451
[
https://issues.apache.org/jira/browse/PIG-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879046#action_12879046
]
Richard Ding commented on PIG-1333:
---
Hi Dmitriy,
I added the new method on JobStats class
[
https://issues.apache.org/jira/browse/PIG-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ding updated PIG-1333:
--
Attachment: PIG-1333_2.patch
> API interface to Pig
>
>
> Key: PIG-1
Gang,
What you are saying can never happen because we create a new MR
operator only when we have a blocking operator which needs to go in
the next MR operator. We dont create new MR operator apriori without
looking at next physical operator in the pipeline. If you are seeing
this happening, I woul
I've never seen a case where this happens. Is this a theoretical
question or are you seeing this issue?
Alan.
On Jun 15, 2010, at 8:49 AM, Gang Luo wrote:
Hi,
Is it possible the last MapReduce job in the MR plan only loads
something and stores it without any other processing in between? F
[
https://issues.apache.org/jira/browse/PIG-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated PIG-1450:
-
Attachment: TEST-org.apache.pig.test.TestAlgebraicEvalLocal.txt
Full test log attached.
> TestAlgebraicEva
There have been several requests for this. I'm not a fan of it,
because it makes it too easy to forget that you're forcing a single
reducer MR job to accomplish this. But I'm open to persuasion if
everyone else disagrees.
Alan.
On Jun 11, 2010, at 7:27 PM, Russell Jurney wrote:
This wou
TestAlgebraicEvalLocal failures due to OOM
--
Key: PIG-1450
URL: https://issues.apache.org/jira/browse/PIG-1450
Project: Pig
Issue Type: Test
Affects Versions: 0.7.0, 0.8.0
Reporter: El
Hi,
Is it possible the last MapReduce job in the MR plan only loads something and
stores it without any other processing in between? For example, when visiting
some physical operator, we need to end the current MR operator after embedding
the physical operator into MR operator, and create a new
For at least simple cases what's in the pseduo code should work. I
hope someday soon we can start using the new logical optimizer work
(in the experimental package) to build rules for the MR optimizer
(like this combiner stuff) as well, which should be much easier to
code. But it will be
[
https://issues.apache.org/jira/browse/PIG-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated PIG-1302:
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Fix Version/
[
https://issues.apache.org/jira/browse/PIG-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878904#action_12878904
]
Giridharan Kesavan commented on PIG-1302:
-
This patch just adds the pigtest target as
20 matches
Mail list logo