Pig Developers,
We have made several significant performance and other improvements over
the last couple of months:
(1) Added an optimizer with several rules
(2) Introduced skew and merge joins
(3) Cleaned COUNT and AVG semantics
I think it is time for another release to
[
https://issues.apache.org/jira/browse/PIG-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy V. Ryaboy updated PIG-923:
--
Status: Patch Available (was: Open)
Allow setting logfile location in pig.properties
Olga,
Do non-commiters get a vote?
Zebra is in trunk, but relies on 0.20, which is somewhat inconsistent
even if it's in contrib/
Would love to see dynamic (or at least static) shims incorporated into
the 0.4 release (see PIG-660, PIG-924)
There are a couple of bugs still outstanding that I
Hi Dmitry,
Non-committers get a non-binding vote.
Zebra needs Hadoop 20.1 because it is relying on TFile functionality that is
not available in Hadoop 20. In general, the recommendation from the Hadoop team
is to wait till hadoop 20.1 is released.
For the remainder of the issues, while I see
I have a question:
Will we be able to fix piggybank sources given that Zebra needs 0.20 and the
rest of Pig requires 0.18?
If the answer is yes then, +1 for the release. I agree with the plan of making
0.4.0 with Hadoop-0.18 and a later release (0.5.0) for Hadoop-0.20.1.
Thanks,
Santhosh
Hi Santhosh,
What do you mean by fixing piggybank?
Olga
-Original Message-
From: Santhosh Srinivasan [mailto:s...@yahoo-inc.com]
Sent: Monday, August 17, 2009 1:37 PM
To: pig-dev@hadoop.apache.org
Subject: RE: Pig 0.4.0 release
I have a question:
Will we be able to fix piggybank
Till we release 0.5.0, will zebra's requirement on 0.20 prevent any bugs/issues
with Piggybank?
Santhosh
-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Monday, August 17, 2009 1:43 PM
To: pig-dev@hadoop.apache.org
Subject: RE: Pig 0.4.0 release
Hi Santhosh,
See
http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/166/changes
Changes:
[olga] PIG-892: Make COUNT and AVG deal with nulls accordingly with SQL
standart(olgan)
--
[...truncated 111335 lines...]
[exec] [junit] 09/08/17
[
https://issues.apache.org/jira/browse/PIG-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744194#action_12744194
]
Hadoop QA commented on PIG-923:
---
-1 overall. Here are the results of testing the latest
[
https://issues.apache.org/jira/browse/PIG-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744216#action_12744216
]
Todd Lipcon commented on PIG-924:
-
Oops, apparently it is Monday and my brain is scrambled.
Rephrasing my question:
Till we release 0.5.0, will zebra's requirement on hadoop-0.20 prevent fixing
of any bugs/issues with Piggybank?
Santhosh
-Original Message-
From: Santhosh Srinivasan [mailto:s...@yahoo-inc.com]
Sent: Monday, August 17, 2009 1:47 PM
To:
[
https://issues.apache.org/jira/browse/PIG-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744238#action_12744238
]
Thejas M Nair commented on PIG-824:
---
JFlex.jar (required for build this patch) can be
Thanks to the PIG team, The first version of contrib project Zebra
(PIG-833) is committed to PIG trunk.
In short, Zebra is a table storage layer built for use in PIG and other
Hadoop applications.
While we are stabilizing current version V1 in the trunk, we plan to add
more new features
+1
-Original Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent: Monday, August 17, 2009 4:06 PM
To: pig-dev@hadoop.apache.org
Subject: Proposal to create a branch for contrib project Zebra
Thanks to the PIG team, The first version of contrib project Zebra
(PIG-833) is
[
https://issues.apache.org/jira/browse/PIG-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744273#action_12744273
]
Daniel Dai commented on PIG-924:
I am reviewing the patch.
Make Pig work with multiple
My vote is -1
-Original Message-
From: Santhosh Srinivasan
Sent: Monday, August 17, 2009 4:38 PM
To: 'pig-dev@hadoop.apache.org'
Subject: RE: Proposal to create a branch for contrib project Zebra
Is there any precedence for such proposals? I am not comfortable with
extending committer
Is there any precedence for such proposals? I am not comfortable with
extending committer access to contrib teams. I would suggest that Zebra
be made a sub-project of Hadoop and have a life of its own.
Santhosh
-Original Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent:
Raghu is PMC member and as such already has committer rights to all
subprojects. So we are not breaking any new grounds here. The reasoning
is the same as for creating branches for Pig multiquery work that we did
in Pig.
Olga
-Original Message-
From: Santhosh Srinivasan
+1
On 8/18/09 7:11 AM, Olga Natkovich ol...@yahoo-inc.com wrote:
+1
-Original Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent: Monday, August 17, 2009 4:06 PM
To: pig-dev@hadoop.apache.org
Subject: Proposal to create a branch for contrib project Zebra
Thanks
[
https://issues.apache.org/jira/browse/PIG-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744305#action_12744305
]
Todd Lipcon commented on PIG-924:
-
Couple notes on the patch:
- you've turned
IANAC, but my (non-binding) vote is also -1. I think all the improvements
and feature addition to zebra should be available through pig trunk. The
codebase is not big enough to justify creating a branch. If the reason is
Pig's dependence on a checked in hadoop jar, the shims proposal by Dmitry
[
https://issues.apache.org/jira/browse/PIG-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744307#action_12744307
]
Dmitriy V. Ryaboy commented on PIG-924:
---
Thanks for looking, Todd -- most of those
[
https://issues.apache.org/jira/browse/PIG-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744310#action_12744310
]
Todd Lipcon commented on PIG-924:
-
Gotcha, thanks for explaining. Aside from the nits, patch
See http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/167/
--
[...truncated 111282 lines...]
[exec] [junit] 09/08/18 01:01:56 INFO dfs.DataNode: PacketResponder 2
for block blk_3027939285115887556_1011 terminating
[exec]
[
https://issues.apache.org/jira/browse/PIG-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744316#action_12744316
]
Hadoop QA commented on PIG-925:
---
-1 overall. Here are the results of testing the latest
On Aug 17, 2009, at 4:38 PM, Santhosh Srinivasan wrote:
Is there any precedence for such proposals? I am not comfortable with
extending committer access to contrib teams. I would suggest that
Zebra
be made a sub-project of Hadoop and have a life of its own.
There has been sufficient
[
https://issues.apache.org/jira/browse/PIG-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744323#action_12744323
]
Jeff Hammerbacher commented on PIG-833:
---
Hey,
Raghu, you mention that a design document
[
https://issues.apache.org/jira/browse/PIG-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744326#action_12744326
]
Jeff Hammerbacher commented on PIG-823:
---
Hey,
Great to see Owl source! I've filed a
That leaves us with contrib committers.
Can you point to earlier email threads that cover the topic of giving
committer access to contrib projects? Specifically, what does it
mean to
award someone committer privileges to a contrib project, what are the
access privileges that come with such
[
https://issues.apache.org/jira/browse/PIG-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy V. Ryaboy updated PIG-911:
--
Status: Open (was: Patch Available)
[Piggybank] SequenceFileLoader
[
https://issues.apache.org/jira/browse/PIG-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy V. Ryaboy updated PIG-911:
--
Attachment: pig_911.2.patch
Addressed Alan's comments.
[Piggybank] SequenceFileLoader
[
https://issues.apache.org/jira/browse/PIG-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744343#action_12744343
]
Dmitriy V. Ryaboy commented on PIG-911:
---
Concerning making this a StoreFunc, as well --
Hi Santosh,
There are two separate things :
(a) voting a contributor as a committer
(b) committing to a contrib project.
(b):
My experience with Hadoop is that Contrib by definition is very
loosely coupled with core. By convention, we as committers to core
(hdfs, mapred, etc) did not have
[
https://issues.apache.org/jira/browse/PIG-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-925:
---
Status: Patch Available (was: Open)
Fix join in local mode
--
Key:
[
https://issues.apache.org/jira/browse/PIG-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-925:
---
Attachment: PIG-925-2.patch
Address the javac warning
Fix join in local mode
--
[
https://issues.apache.org/jira/browse/PIG-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-925:
---
Status: Open (was: Patch Available)
Fix join in local mode
--
Key:
See http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/168/
[
https://issues.apache.org/jira/browse/PIG-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744373#action_12744373
]
Hadoop QA commented on PIG-911:
---
+1 overall. Here are the results of testing the latest
Raghu Angadi wrote:
Hi Santosh,
There are two separate things :
(a) voting a contributor as a committer
(b) committing to a contrib project.
[...]
Reason for (a) is simple scalability. We can not monitor everything. If
I meant to say Reason for (b) (why contrib commits are treated bit
39 matches
Mail list logo
