Hi,
I have created a candidate build for Pig 0.1.1. This release is almost
identical to Pig 0.1.0 with a couple of exceptions:
(1) It is integrated with hadoop 18
(2) It has one small bug fix (PIG-253)
(3) Several UDF were added to piggybank - pig's UDF repository
The rat report is attached.

Hi,
I am happy to announce that Hadoop PMC voted to make Pradeep Kamath and
Santhosh Srinivasan Pig Committer to acknowledge their significant
contribution to the project!
Congratulation to Santhosh and Pradeep!
Olga

The reason trunk does not contain the latest code is that Pig has
undergone a complete redesign that we could not do incrementally on the
trunk without jeopardizing its stability. The decision was made to do
the work on a brunch and then merge branch code to the trunk when it is
stable.
The

Hi,
This is to announce that as of now Pig requires Java 1.6 to build and
run the system. This allows Pig to take advantage of the new features
available in 1.6 and any performance improvements. This is also in line
with Hadoop move to Java 1.6 a few month back.
Olga

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

Pig Developers and Committers,
Now that types branch is merged into trunk and the dust settled, I
propose that it is time for the next release.
I propose that we name this release as Pig 1.0.0 since this is a major
rework and a much more stable and performant code with stable
interfaces.

Committers,
I just branched for Pig 1.0 release. As part of the release, I
resturctured CHANGES.txt to match the format used by Hadoop.
One major change from how we used to do it is that most recent changes
go to the top of the file (not to the bottom as we used to do.)
I added the following

Pig Committers,
I have created a candidate build for Pig 1.0.0.
This release represents a major rewrite of Pig from the parser down. It
also introduced type system into Pig and greatly improved system
performance.
The rat report is attached. Note that there are many java files listed
as being

Hi Guys,
As you know I am going to be out of the office from 3/20-4/3.
I asked you to cover the following areas for me:
Pradeep:
- Working with Solutions team to triage bugs and decide which ones need
to be fixed right-away. If in doubt, come and talk to him :).
- My hope is that we would

The branch is there now.
If you commit any changes that are relevant for the release, please,
make sure to commit them both to trunk and to the branch. Also make sure
to update CHANGES.txt in both places.
Olga
-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent

Hi,
I created a candidate build for Pig 0.3.0 release. The main feature of
this release is support for multiquery which allows to share computation
across multiple queries within the same script. We see significant
performance improvements (up to order of magnitude) as the result of
this

Hi,
Thanks for everybody who voted!
We have four +1 binding votes from PMC members Arun Murthy, Nigel Daley,
Alan Gates, and Olga Natkovich. We have three +1 non-binding votes from
Pig Committers Pradeep Kamath, Daniel Dai, and Santhosh Srinivasan
There are no -1 votes. Also sufficient time

Pig Team is happy to announce Pig 0.3.0 release!
Pig is a Hadoop subproject that provides high-level data-flow language
and an execution framework for parallel computation on a Hadoop cluster.
More details about Pig can be found at http://hadoop.apache.org/pig/.
The highlight of this release

Hi,
The current implementation of COUNT and AVG in Pig counts null values.
This is inconsistent with SQL semantics and also with semantics of other
aggregated functions such as SUM, MIN, and MAX. Originally we chose this
implementation for performance reasons; however, we re-implemented both

At the moment we can't make UDFs dependant on Hadoop as people also use
them for testing in local mode which is currently not based on Hadoop
local mode due to performance constrains.
I agree that we need to provide a way to get UDF a
configuration/property object.
Olga
-Original

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

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

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
-Original Message-
From: Olga Natkovich [mailto:ol

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

To answer Santhosh's question. I think the plan is to move to Jflex and CUP but
when that happens is a matter of priorities and resources which are not clear
at this point. We do welcome contributions ;).
Olga
-Original Message-
From: Thejas Nair [mailto:te...@yahoo-inc.com]
Sent:

I am having some problems with the docs that I will need to resolve
tomorrow. I would like to keep the tree closed till then. If you
absolutely need to make a checkin, please, go ahead and I will integrate
your patch into the branch.
Thanks,
Olga
-Original Message-
From: Olga Natkovich

Hi,
As you know, a lot of work this year went into performance optimization
of Pig. One of the main sources of performance problems is high memory
usage. In an effort to address this problem we propose switching
internal implementation of strings from Java Strings to Hadoop Text
because text

Hi,
I created a candidate build for Pig 0.4.0 release. The highlights of
this release are
- Performance improvements especially in the area of JOIN
support where we introduced two new join types: skew join to deal with
data skew and sort merge join to take advantage of the sorted

Since we have not heard any objections, we are going to proceed with
this plan. Stay tuned for the details when the change is coming.
Olga
-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Friday, September 11, 2009 11:54 AM
To: pig-dev@hadoop.apache.org; pig-u

With 3 +1s from Hadoop PMC (Alan Gates, Raghu Angadi, and Olga
Natkovich) and no -1s, the release passed the vote. I will be working on
rolling it out next.
Olga
-Original Message-
From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
Sent: Tuesday, September 22, 2009 4:12 PM
To: priv

Pig Team is happy to announce Pig 0.4.0 release!
Pig is a Hadoop subproject that provides high-level data-flow language
and an execution framework for parallel computation on a Hadoop cluster.
More details about Pig can be found at http://hadoop.apache.org/pig/.
This release introduces two

Hi,
I created a candidate build for Pig 0.5.0 release. It contains the same
functionality as Pig 0.4.0 except it works with Hadoop 20.x releases.
I ran the release audit and rat report looked fine. The relevant part is
attached below.
Keys used to sign the release are available at

Pig Team is happy to announce Pig 0.5.0 release!
Pig is a Hadoop subproject that provides high-level data-flow language
and an execution framework for parallel computation on a Hadoop cluster.
More details about Pig can be found at http://hadoop.apache.org/pig/.
This release makes

Hi,
I would like to propose to branch for Pig 0.6.0 release with the intent
to have a release before the end of the year. We have done a lot of work
since branching for Pig 0.5.0 that we would like to share with users.
This includes changing how bags are spilled onto disk (PIG-975,
PIG-1037),

, 2009, at 12:26 PM, Olga Natkovich wrote:
Hi,
I would like to propose to branch for Pig 0.6.0 release with the
intent
to have a release before the end of the year. We have done a lot of
work
since branching for Pig 0.5.0 that we would like to share with users.
This includes changing

I created the branch. Trunk is open for commits.
Olga
-Original Message-
From: Olga Natkovich
Sent: Thursday, November 12, 2009 10:46 AM
To: 'pig-dev@hadoop.apache.org'
Subject: RE: [VOTE] Branch for Pig 0.6.0 release
We have 4 +1 votes for this and no -1s. I am about to create 0.6.0

Hi Garrit,
It would be great if you could contribute the code. The process is
pretty simple:
- Open a JIRA that describes what the loader does and that you would
like to contribute it to the Piggybank.
- Submit the patch that contains the loader. Make sure it has unit tests
and javadoc.
On this

not really wild about creating a new section of contrib just for
functions that have heavier weight requirements.
Alan.
-D
On Mon, Nov 30, 2009 at 3:09 PM, Olga Natkovich ol...@yahoo-
inc.com wrote:
Hi Garrit,
It would be great if you could contribute the code. The process is
pretty

Hi,
As many of you now we are actively working on Load-Store redesign for
Pig. This work is documented in
http://wiki.apache.org/pig/LoadStoreRedesignProposal and is happening on
a separate branch with intent to merge is back into the trunk early next
year. We need to figure out a way to keep

Pig Developers,
Since we have branched for the release, we have fixed a lot of bugs and
stabilized the code quite a bit. There are no outstanding blockers for
0.6.0.
I suggest that we cut the release. Please, let me know if you have any
objections; otherwise, I will start the release

in 0.6 that are not backwards-compatible, or is
all that only in trunk?
-Dmitriy
On Thu, Jan 7, 2010 at 10:33 AM, Olga Natkovich ol...@yahoo-inc.com
wrote:
Pig Developers,
Since we have branched for the release, we have fixed a lot of bugs
and
stabilized the code quite a bit

: Thursday, January 07, 2010 10:44 AM
To: pig-dev@hadoop.apache.org
Subject: Re: time to release Pig 0.6.0
Olga,
Are there any changes in 0.6 that are not backwards-compatible, or is
all that only in trunk?
-Dmitriy
On Thu, Jan 7, 2010 at 10:33 AM, Olga Natkovich ol...@yahoo-inc.com
wrote:
Pig

@hadoop.apache.org
Subject: Re: time to release Pig 0.6.0
Having just been hit by this -- any chance we can put
http://issues.apache.org/jira/browse/PIG-1075 into 0.6?
On Thu, Jan 7, 2010 at 10:49 AM, Olga Natkovich ol...@yahoo-inc.com
wrote:
As far as we know, there are no changes in 0.6.0 that break

Hi,
It is my pleasure to announce that Pig now has two new committers -
Ashutosh Chauhan and Richard Ding. Both Ashutosh and Richard have made
significant contributions to Pig and we are glad to have them on board!
Olga

Pig Developers,
As most of you know, we have spent the last couple of month mostly
working on LSR branch. We believe that in about a week the code in the
branch will be stable enough to merge it back into the trunk.
If you are using trunk or making any modifications to it, you will be

Hi,
I would like to welcome Thejas Nair as our newest Pig committer. Thejas
has been contributing to Pig for over a year now. He is the main
contributor to Pig SQL effort. He also has done significant work on LSR
project by porting merge join to the new platform. Thejas is active on
the

Hi,
It has been a few weeks since we merged the Load-Store redesign changes
into the trunk. We have been doing a lot of testing and fixing bugs. I
think it is time to branch the code in preparation for Pig 0.7.0
release. Unless I here objections, I will do this next Monday, 3/22.
Olga

Hi,
If you have an issue assigned to you for Pig 0.7.0 release, please, make
sure that it can be committed by the end of the week since we are aiming
to branch for the release by next Monday, 3/22. If you don't think the
issue can be addressed by then but feel strongly that it needs to be in

This is because Hadoop 20 does not support distributed cache in local
mode. My understanding is that it would be part of Hadoop 22.
Olga
-Original Message-
From: Gang Luo [mailto:lgpub...@yahoo.com.cn]
Sent: Monday, June 07, 2010 3:40 PM
To: pig-dev@hadoop.apache.org
Subject:

Pig Developers,
I would like to propose that we branch for Pig 0.8.0 at the end of
August and plan for the release by the end of October. Please, let me
know if you see problem with either of the dates.
If you are planning to contribute any patches to Pig 0.8.0, please, make
sure that you

CONCAT act on all fields of a
tuple, instead of just the first two fields of a tuple
I can hack on this this weekend. Sorry for the absence on the JIRAs, been
slammed on work stuff.
Russ
On Tue, Aug 17, 2010 at 2:46 PM, Olga Natkovich (JIRA) j...@apache.orgwrote:
[
https

2010.
I nominate Olga Natkovich as the chair of the PMC. (PMC chairs have
no more power than other PMC members, but they are responsible for
writing regular reports for the Apache board, assigning rights to new
committers, etc.)
I propose that as part of the resolution that will be forwarded

Guys,
After spending the last couple of days collecting information for Pig 0.8.0
documentation, I would like to propose a change for our patch process that
would make my life easier :).
I would like to ask developers working on patches with new customer facing
features or user visible

Hi guys,
We are considering switching from ant to maven as the build system for Pig
starting with 0.9 release. Details of maven project are here
http://maven.apache.org/. The main motivation is that core hadoop is already in
the process of switching and having a consistent build system is

Dear Pig Users and Developers,
ASF board just voted for Pig to become TLP. Please, see board notes below. Over
the next several weeks we will be moving our infrastructure out of Hadoop. You
can keep track of the progress by following this JIRA:
https://issues.apache.org/jira/browse/INFRA-3005.

: Olga Natkovich
Fix For: types_branch
Many users liked the verbose outout currently available on trunk. In
particular, the fact that MR job progress was available.
While we don't want to have it enable by default because it is very verbose and
also Hadoop specific, we could a flag

Type: Bug
Reporter: Olga Natkovich
It does so for scalar types but not for complext types and not for the fields
inside of the complext types.
This is because it uses different code to parse scalar types by themselves and
scalar types inside of a complex type. It should really use

[
https://issues.apache.org/jira/browse/PIG-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652067#action_12652067
]
Olga Natkovich commented on PIG-547:
Hi Craig,
Thanks for the patch!
Is this for trunk

[
https://issues.apache.org/jira/browse/PIG-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12662093#action_12662093
]
Olga Natkovich commented on PIG-573:
We will need to make an additional change