[jira] Commented: (PIG-1001) Generate more meaningful error message when one input file does not exist

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776545#action_12776545
 ] 

Nigel Daley commented on PIG-1001:
--

Please ensure the issue is "Assigned" to the patch author when committing.

Also, please provide a justification for why there is no unit test, then 
describe how you DID test it before you uploaded the patch.

> Generate more meaningful error message when one input file does not exist
> -
>
> Key: PIG-1001
> URL: https://issues.apache.org/jira/browse/PIG-1001
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.4.0
>Reporter: Daniel Dai
> Fix For: 0.6.0
>
> Attachments: PIG-1001-1.patch, PIG-1001-2.patch
>
>
> In the following query, if 1.txt does not exist, 
> a = load '1.txt';
> b = group a by $0;
> c = group b all;
> dump c;
> Pig throws error message "ERROR 2100: file:/tmp/temp155054664/tmp1144108421 
> does not exist.", Pig should deal with it with the error message "Input file 
> 1.txt not exist" instead of those confusing messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release Pig 0.4.0 (candidate 1)

[Nigel Daley]

Is anyone else getting javac errors running "ant test"?

compile-sources:
[javac] Compiling 484 source files to /Users/ndaley/hadoop/verify/ 
pig-0.4.0/build/classes
[javac] /Users/ndaley/hadoop/verify/pig-0.4.0/src/org/apache/pig/ 
ComparisonFunc.java:22: package org.apache.hadoop.io does not exist

[javac] import org.apache.hadoop.io.WritableComparable;
[javac]^
...

Nige

On Sep 17, 2009, at 12:09 PM, Olga Natkovich wrote:


Hi,

I have fixed the issue causing the failure that Alan reported.

Please test the new release:
http://people.apache.org/~olga/pig-0.4.0-candidate-1/.

Vote closes on Tuesday, 9/22.

Olga


-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Monday, September 14, 2009 2:06 PM
To: pig-dev@hadoop.apache.org; priv...@hadoop.apache.org
Subject: [VOTE] Release Pig 0.4.0 (candidate 0)

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 data  
sets.


-  Support for Outer join.

-  Works with Hadoop 18



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
http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup.



Please download the release and try it out:
http://people.apache.org/~olga/pig-0.4.0-candidate-0.



Should we release this? Vote closes on Thursday, 9/17.



Olga





[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/contrib/ 
CHANGES.txt

[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/contrib/zebra/ 
CHANG

ES.txt
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/broken- 
links.x

ml
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/ 
cookbook.html

[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/index.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/linkmap.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/ 
piglatin_refer

ence.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/ 
piglatin_users

.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/setup.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/ 
tutorial.html

[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/udf.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/api/ 
package-li

st
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes.

html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
missingS

inces.txt
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
user_com

ments_for_pig_0.3.1_to_pig_0.5.0-dev.xml
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

alldiffs_index_additions.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

alldiffs_index_all.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

alldiffs_index_changes.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

alldiffs_index_removals.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

changes-summary.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

classes_index_additions.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

classes_index_all.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

classes_index_changes.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

classes_index_removals.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

constructors_index_additions.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

constructors_index_all.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

constructors_index_changes.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

constructors_index_removals.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

fields_index_additions.html
[java]  !?
/home/olgan/src/pig-apache/trunk/build/pig-0.5.0-dev/docs/jdiff/ 
changes/

fields_index_all.html
[java]  !?
/home/

Re: [VOTE] Release Pig 0.3.0 (candidate 0)

[Nigel Daley]

+1.

On Jun 18, 2009, at 12:30 PM, Olga Natkovich wrote:


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 optimization.

I ran the rat report and made sure that all the source files contain
proper headers. (Not attaching the report since it caused trouble with
the last release.)

Keys used to sign the release candidate are at
http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS.

Please, download and try the release candidate:
http://people.apache.org/~olga/pig-0.3.0-candidate-0/.

Please, vote by Wednesday, June 24th.

Olga

[jira] Commented: (PIG-854) The automated build process should publish the diff in compiler warning messages

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720504#action_12720504
 ] 

Nigel Daley commented on PIG-854:
-

I believe this can be done by the Warnings hudson plugin.

> The automated build process should publish the diff in compiler warning 
> messages
> 
>
> Key: PIG-854
> URL: https://issues.apache.org/jira/browse/PIG-854
> Project: Pig
>  Issue Type: Bug
>  Components: build
>Affects Versions: 0.3.0
> Environment: Hudson
>Reporter: Santhosh Srinivasan
>Assignee: Giridharan Kesavan
> Fix For: 0.3.0
>
>
> Currently, the automated build process publishes a report that captures the 
> difference in the number of warning messages due to a patch from that of 
> trunk However, the details of the new warning messages are not listed. For 
> findbugs, a url that contains the details is published. A similar page is 
> required for the compiler warning messages.
> For reference, check out 
> https://issues.apache.org/jira/browse/PIG-697?focusedCommentId=12720326&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12720326
> The console output has the following line. Note that the details are stored 
> on the build machine. Its not exported as a web page for users to figure out 
> the details. At least,  I was not able to do so. It would be extremely 
> helpful (I would say mandatory) to expose the details. If these details are 
> already present then please point me to the right location.
> {code}
> [exec] /home/hudson/tools/ant/latest/bin/ant  -Djavac.args=-Xlint -Xmaxwarns 
> 1000 -Declipse.home=/home/nigel/tools/eclipse/latest 
> -Djava5.home=/home/hudson/tools/java/latest1.5 
> -Dforrest.home=/home/nigel/tools/forrest/latest -DPigPatchProcess= clean tar 
> > 
> /home/hudson/hudson-slave/workspace/Pig-Patch-minerva.apache.org/patchprocess/patchJavacWarnings.txt
>  2>&1
>  [exec] There appear to be 224 javac compiler warnings before the patch 
> and 259 javac compiler warnings after applying the patch.
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-854) The automated build process should publish the diff in compiler warning messages

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720384#action_12720384
 ] 

Nigel Daley commented on PIG-854:
-

Get the project javac and javadoc warnings to 0 and then this becomes a 
non-issue.  That's what Hadoop is working on.

> The automated build process should publish the diff in compiler warning 
> messages
> 
>
> Key: PIG-854
> URL: https://issues.apache.org/jira/browse/PIG-854
> Project: Pig
>  Issue Type: Bug
>  Components: build
>Affects Versions: 0.3.0
> Environment: Hudson
>Reporter: Santhosh Srinivasan
>Assignee: Giridharan Kesavan
> Fix For: 0.3.0
>
>
> Currently, the automated build process publishes a report that captures the 
> difference in the number of warning messages due to a patch from that of 
> trunk However, the details of the new warning messages are not listed. For 
> findbugs, a url that contains the details is published. A similar page is 
> required for the compiler warning messages.
> For reference, check out 
> https://issues.apache.org/jira/browse/PIG-697?focusedCommentId=12720326&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12720326
> The console output has the following line. Note that the details are stored 
> on the build machine. Its not exported as a web page for users to figure out 
> the details. At least,  I was not able to do so. It would be extremely 
> helpful (I would say mandatory) to expose the details. If these details are 
> already present then please point me to the right location.
> {code}
> [exec] /home/hudson/tools/ant/latest/bin/ant  -Djavac.args=-Xlint -Xmaxwarns 
> 1000 -Declipse.home=/home/nigel/tools/eclipse/latest 
> -Djava5.home=/home/hudson/tools/java/latest1.5 
> -Dforrest.home=/home/nigel/tools/forrest/latest -DPigPatchProcess= clean tar 
> > 
> /home/hudson/hudson-slave/workspace/Pig-Patch-minerva.apache.org/patchprocess/patchJavacWarnings.txt
>  2>&1
>  [exec] There appear to be 224 javac compiler warnings before the patch 
> and 259 javac compiler warnings after applying the patch.
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: pig patch test process.

[Nigel Daley]

FYI,

This happens when the hudson machine goes down for long enough that  
pig-dev emails to it start bouncing and it then get automatically  
unsubscribed.


Nige

On Jun 8, 2009, at 9:43 AM, Giridharan Kesavan wrote:


pigqa email alias got unsubscribed to pig-dev mailing list.

Today morning(IST) I ve subscribed pigqa to pig-dev mailing list  
again.


If you don't see your patch listed in the patch queue please  
resubmit your patch.

http://hudson.zones.apache.org/hudson/view/Pig/job/Pig-Patch-Admin/lastSuccessfulBuild/artifact/PIG_PatchQueue.html

I've resubmitted pig-839 & pig-835

Thanks,
Giri

[jira] Commented: (PIG-701) Implement IVY for resolving pig dependencies

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703442#action_12703442
 ] 

Nigel Daley commented on PIG-701:
-

Looks good.  Should we move to the same version of Junit as Hadoop (4.5)?  
Other than that, +1.

> 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
> Attachments: lib_rm.sh, 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.

[jira] Commented: (PIG-765) to implement jdiff

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702422#action_12702422
 ] 

Nigel Daley commented on PIG-765:
-

+1 code review.

> to implement jdiff
> --
>
> Key: PIG-765
> URL: https://issues.apache.org/jira/browse/PIG-765
> Project: Pig
>  Issue Type: Improvement
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: pig-765.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-762) to move the test logs and hadoop job logs to diff location

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697546#action_12697546
 ] 

Nigel Daley commented on PIG-762:
-

Giri, why ${basedir}/test/logsi/hadoop?  I'd suggest logsi be something more 
descriptive.

> to move the test logs and hadoop job logs to diff location 
> ---
>
> Key: PIG-762
> URL: https://issues.apache.org/jira/browse/PIG-762
> Project: Pig
>  Issue Type: Improvement
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: pig-762.patch
>
>
> junit test logs and hadoop logs are put in the same build/test/logs folder .. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-743) to implement clover

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697392#action_12697392
 ] 

Nigel Daley commented on PIG-743:
-

+1 code review.

> to implement clover
> ---
>
> Key: PIG-743
> URL: https://issues.apache.org/jira/browse/PIG-743
> Project: Pig
>  Issue Type: Improvement
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: pig-743.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release Pig 1.0.0 (candidate 0)

[Nigel Daley]

BTW, at this point I'm more concerned that we get a release out than  
what it is called.  I do think Pig is stable enough for 1.0 but I'm  
not willing to let version numbering get in the way of getting a  
release out.  More frequent releases is better for the community.


Nige

On Mar 23, 2009, at 1:30 PM, Nigel Daley wrote:


+1.

On Mar 23, 2009, at 1:26 PM, Alan Gates wrote:

To address Santhosh's concerns that 1.0 is not an appropriate  
release number, I propose that we release the same code under the  
name 0.2.0.


Alan.

On Mar 20, 2009, at 11:54 AM, Santhosh Srinivasan wrote:

-1 on the 1.0.0 release. IMHO, Pig is relatively stable but not  
quite

there. I would prefer 0.2.0

1. 1.0.0 signifies a highly stable and solid release which will  
require

a little bit more work.
2. Multi-query support will break the way users are using grunt
3. There are ongoing efforts for changing load and/or store  
interfaces


Santhosh

-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Tuesday, March 17, 2009 3:21 PM
To: pig-dev@hadoop.apache.org
Subject: [VOTE] Release Pig 1.0.0 (candidate 0)

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 without a license header. All these files are generated by
javacc.

Keys used to sign the release are available at
http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup.

Please download, test, and try it out:

http://people.apache.org/~olga/pig-1.0.0-candidate-0
<http://people.apache.org/~olga/pig-1.0.0-candidate-0>

Should we release this? Vote closes on Friday, March 20th.

Olga

Re: [VOTE] Release Pig 1.0.0 (candidate 0)

[Nigel Daley]

+1.

On Mar 23, 2009, at 1:26 PM, Alan Gates wrote:

To address Santhosh's concerns that 1.0 is not an appropriate  
release number, I propose that we release the same code under the  
name 0.2.0.


Alan.

On Mar 20, 2009, at 11:54 AM, Santhosh Srinivasan wrote:


-1 on the 1.0.0 release. IMHO, Pig is relatively stable but not quite
there. I would prefer 0.2.0

1. 1.0.0 signifies a highly stable and solid release which will  
require

a little bit more work.
2. Multi-query support will break the way users are using grunt
3. There are ongoing efforts for changing load and/or store  
interfaces


Santhosh

-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Tuesday, March 17, 2009 3:21 PM
To: pig-dev@hadoop.apache.org
Subject: [VOTE] Release Pig 1.0.0 (candidate 0)

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 without a license header. All these files are generated by
javacc.

Keys used to sign the release are available at
http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup.

Please download, test, and try it out:

http://people.apache.org/~olga/pig-1.0.0-candidate-0


Should we release this? Vote closes on Friday, March 20th.

Olga

Re: [VOTE] Release Pig 1.0.0 (candidate 0)

[Nigel Daley]

Not every decision is done by calling for a formal vote.  No one -1'd  
Olga's proposal.


nige.

On Mar 20, 2009, at 1:51 PM, Santhosh Srinivasan wrote:


Nigel,

It was a discussion without the call for a vote. I am attaching the
email that was sent out back then.

Thanks,
Santhosh

-Original Message-----
From: Nigel Daley [mailto:nda...@yahoo-inc.com]
Sent: Friday, March 20, 2009 1:41 PM
To: pig-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Pig 1.0.0 (candidate 0)

Santhosh, the version numbering was discussed on this list almost 2
weeks ago.  Why didn't you participate then?

Nige

On Mar 20, 2009, at 11:54 AM, Santhosh Srinivasan wrote:


-1 on the 1.0.0 release. IMHO, Pig is relatively stable but not quite
there. I would prefer 0.2.0

1. 1.0.0 signifies a highly stable and solid release which will
require
a little bit more work.
2. Multi-query support will break the way users are using grunt
3. There are ongoing efforts for changing load and/or store  
interfaces


Santhosh

-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Tuesday, March 17, 2009 3:21 PM
To: pig-dev@hadoop.apache.org
Subject: [VOTE] Release Pig 1.0.0 (candidate 0)

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 without a license header. All these files are generated by
javacc.

Keys used to sign the release are available at
http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup.

Please download, test, and try it out:

http://people.apache.org/~olga/pig-1.0.0-candidate-0
<http://people.apache.org/~olga/pig-1.0.0-candidate-0>

Should we release this? Vote closes on Friday, March 20th.

Olga



From: "Olga Natkovich" 
Date: March 6, 2009 5:28:36 PM PST
To: 
Subject: Next pig release
Reply-To: 


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.

Olga

Re: [VOTE] Release Pig 1.0.0 (candidate 0)

[Nigel Daley]

Santhosh, the version numbering was discussed on this list almost 2  
weeks ago.  Why didn't you participate then?


Nige

On Mar 20, 2009, at 11:54 AM, Santhosh Srinivasan wrote:


-1 on the 1.0.0 release. IMHO, Pig is relatively stable but not quite
there. I would prefer 0.2.0

1. 1.0.0 signifies a highly stable and solid release which will  
require

a little bit more work.
2. Multi-query support will break the way users are using grunt
3. There are ongoing efforts for changing load and/or store interfaces

Santhosh

-Original Message-
From: Olga Natkovich [mailto:ol...@yahoo-inc.com]
Sent: Tuesday, March 17, 2009 3:21 PM
To: pig-dev@hadoop.apache.org
Subject: [VOTE] Release Pig 1.0.0 (candidate 0)

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 without a license header. All these files are generated by
javacc.

Keys used to sign the release are available at
http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup.

Please download, test, and try it out:

http://people.apache.org/~olga/pig-1.0.0-candidate-0


Should we release this? Vote closes on Friday, March 20th.

Olga

[jira] Commented: (PIG-725) javadoc: warning - Multiple sources of package comments found for package "org.apache.commons.logging"

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683706#action_12683706
 ] 

Nigel Daley commented on PIG-725:
-

+1 code review.

> javadoc: warning - Multiple sources of package comments found for package 
> "org.apache.commons.logging"
> --
>
> Key: PIG-725
> URL: https://issues.apache.org/jira/browse/PIG-725
> Project: Pig
>  Issue Type: Improvement
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-725.patch, PIG-725.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-700) To automate the pig patch test process

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683115#action_12683115
 ] 

Nigel Daley commented on PIG-700:
-

+1 looks good.

> To automate the pig patch test process
> --
>
> Key: PIG-700
> URL: https://issues.apache.org/jira/browse/PIG-700
> Project: Pig
>  Issue Type: New Feature
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-718) To add standard ant targets to build.xml file

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681920#action_12681920
 ] 

Nigel Daley commented on PIG-718:
-

+1 code review.

> To add standard ant targets to build.xml file 
> --
>
> Key: PIG-718
> URL: https://issues.apache.org/jira/browse/PIG-718
> Project: Pig
>  Issue Type: Sub-task
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-718.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-711) Implement checkstyle for pig

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680744#action_12680744
 ] 

Nigel Daley commented on PIG-711:
-

+1 code review.

> Implement checkstyle for pig
> 
>
> Key: PIG-711
> URL: https://issues.apache.org/jira/browse/PIG-711
> Project: Pig
>  Issue Type: Sub-task
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-711.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-708) implement releaseaudit tart to use rats on pig

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680648#action_12680648
 ] 

Nigel Daley commented on PIG-708:
-

+1 code review.

> implement releaseaudit tart to use rats on pig
> --
>
> Key: PIG-708
> URL: https://issues.apache.org/jira/browse/PIG-708
> Project: Pig
>  Issue Type: Sub-task
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-708.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-706) Implement ant target to use findbugs on PIG

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680647#action_12680647
 ] 

Nigel Daley commented on PIG-706:
-

+1 code review.

> Implement ant target to use findbugs on PIG
> ---
>
> Key: PIG-706
> URL: https://issues.apache.org/jira/browse/PIG-706
> Project: Pig
>  Issue Type: Sub-task
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-706.patch
>
>
> To enable findbugs target for pig

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-699) Implement forrest docs target in Pig Build

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680643#action_12680643
 ] 

Nigel Daley commented on PIG-699:
-

Disregard my comment.  These images aren't needed and won't be committed by 
this patch.

+1.  Please commit.

> Implement forrest docs target in Pig Build
> --
>
> Key: PIG-699
> URL: https://issues.apache.org/jira/browse/PIG-699
> Project: Pig
>  Issue Type: New Feature
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-699.patch, PIG-699.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-699) Implement forrest docs target in Pig Build

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680370#action_12680370
 ] 

Nigel Daley commented on PIG-699:
-

The patch looks like it includes some images which aren't in the patch:

{quote}
Index: src/docs/src/documentation/resources/images/sub-dir/icon-c.png
===
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: 
src/docs/src/documentation/resources/images/sub-dir/icon-c.png
___
Added: svn:mime-type
   + application/octet-stream
{quote}

> Implement forrest docs target in Pig Build
> --
>
> Key: PIG-699
> URL: https://issues.apache.org/jira/browse/PIG-699
> Project: Pig
>  Issue Type: New Feature
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-699.patch, PIG-699.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Next pig release

[Nigel Daley]

If we're committing to backward compatibility for a while, then I'd +1  
1.0.0.  I think Pig is stable enough.


Nige

On Mar 9, 2009, at 1:02 PM, Alan Gates wrote:

+1 on doing a release.  +0 on calling it 1.0.  Are we really that  
stable?


Alan.

On Mar 6, 2009, at 5:28 PM, Olga Natkovich wrote:


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.

Olga

[jira] Commented: (PIG-701) Implement IVY for resolving pig dependencies

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679795#action_12679795
 ] 

Nigel Daley commented on PIG-701:
-

+1

> 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
>
> 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.

[jira] Commented: (PIG-700) To automate the pig patch test process

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679780#action_12679780
 ] 

Nigel Daley commented on PIG-700:
-

Giri, why not get the findbugs and rat targets into Pig first and then run the 
exact same test-patch.sh script that Hadoop does?



> To automate the pig patch test process
> --
>
> Key: PIG-700
> URL: https://issues.apache.org/jira/browse/PIG-700
> Project: Pig
>  Issue Type: New Feature
>  Components: build
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-701) Implement IVY for resolving pig dependencies

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679779#action_12679779
 ] 

Nigel Daley commented on PIG-701:
-

Will this include Hadoop too?  If so, do Hadoop jars need to be published into 
the apache repo?

I suspect we may want to tackle the Hadoop dependency in another Jira as it 
could take some time.

> 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
>
> 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.

[jira] Updated: (PIG-699) Implement forrest docs target in Pig Build

[Nigel Daley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PIG-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nigel Daley updated PIG-699:


Assignee: Giridharan Kesavan

> Implement forrest docs target in Pig Build
> --
>
> Key: PIG-699
> URL: https://issues.apache.org/jira/browse/PIG-699
> Project: Pig
>  Issue Type: New Feature
>Reporter: Giridharan Kesavan
>Assignee: Giridharan Kesavan
> Attachments: PIG-699.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (PIG-699) Implement forrest docs target in Pig Build

[Nigel Daley (JIRA)]

[ 
https://issues.apache.org/jira/browse/PIG-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679644#action_12679644
 ] 

Nigel Daley commented on PIG-699:
-

Giri, do the files in
src/docs/src/documentation/content/xdocs/samples
need to be in the patch?  My guess is no.

Also, it should be stated that this patch changes the "doc" target to "docs".

> Implement forrest docs target in Pig Build
> --
>
> Key: PIG-699
> URL: https://issues.apache.org/jira/browse/PIG-699
> Project: Pig
>  Issue Type: New Feature
>Reporter: Giridharan Kesavan
> Attachments: PIG-699.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

RE: [VOTE] Release Pig 0.1.1 (candidate 0)

[Nigel Daley]

+1.  Signature and MD5 check out.  Unit tests pass.

Nige


From: Olga Natkovich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2008 3:59 PM
To: pig-dev@hadoop.apache.org
Subject: [VOTE] Release Pig 0.1.1 (candidate 0)

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.

Keys used to sign the release are available at http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup 
.


Please download, test, and try it out:

http://people.apache.org/~olga/pig-0.1.1-candidate-0

Should we release this? Vote closes on Wednesday, December 3rd.

Olga