[jira] [Updated] (PIG-1825) ability to turn off the write ahead log for pig's HBaseStorage

[Bill Graham (JIRA)]

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

Bill Graham updated PIG-1825:
-

Attachment: PIG-1825_1.patch

Attached is PIG-1825_1.patch that's updated to apply to the trunk that also 
contains a passing unit test.

> ability to turn off the write ahead log for pig's HBaseStorage
> --
>
> Key: PIG-1825
> URL: https://issues.apache.org/jira/browse/PIG-1825
> Project: Pig
>  Issue Type: Improvement
>Affects Versions: 0.8.0
>Reporter: Corbin Hoenes
>Priority: Minor
> Attachments: HBaseStorage_noWAL.patch, PIG-1825_1.patch
>
>
> Added an option to allow a caller of HBaseStorage to turn off the 
> WriteAheadLog feature while doing bulk loads into hbase.
> From the performance tuning wikipage: 
> http://wiki.apache.org/hadoop/PerformanceTuning
> "To speed up the inserts in a non critical job (like an import job), you can 
> use Put.writeToWAL(false) to bypass writing to the write ahead log."
> We've tested this on HBase 0.20.6 and it helps dramatically.  
> The -noWAL options is passed in just like other options for hbase storage:
> STORE myalias INTO 'MyTable' USING 
> org.apache.pig.backend.hadoop.hbase.HBaseStorage('mycolumnfamily:field1 
> mycolumnfamily:field2','-noWAL');
> This would be my first patch so please educate me with any steps I need to 
> do.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-1946) HBaseStorage constructor syntax is error prone

[Bill Graham (JIRA)]

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

Bill Graham updated PIG-1946:
-

Fix Version/s: 0.10
   Status: Patch Available  (was: Open)

This patch is ready for review. It allows commas and/or spaces to be used as 
column delimiters.

> HBaseStorage constructor syntax is error prone
> --
>
> Key: PIG-1946
> URL: https://issues.apache.org/jira/browse/PIG-1946
> Project: Pig
>  Issue Type: Improvement
>Reporter: Bill Graham
>Assignee: Bill Graham
> Fix For: 0.10
>
> Attachments: PIG-1946_1.patch
>
>
> Using {{HBaseStorage}} like so seems like a reasonable thing to do, but it 
> will yield unexpected results:
> {code}
> STORE result INTO 'hbase://foo' USING
>  org.apache.pig.backend.hadoop.hbase.HBaseStorage(
>  'info:first_name, info:last_name');
> {code}
> The problem us that a column named {{info:first_name,}} will be created, with 
> the trailing comma included. I've had numerous developers get tripped up on 
> this issue since everywhere else in Pig variables are separated by commas, so 
> I propose we fix it.
> I propose we trim leading/trailing commas from column names, but I'm open to 
> other ideas.
> Also should we accept column names that are comman-delimited without spaces?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-1946) HBaseStorage constructor syntax is error prone

[Bill Graham (JIRA)]

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

Bill Graham updated PIG-1946:
-

Attachment: PIG-1946_1.patch

> HBaseStorage constructor syntax is error prone
> --
>
> Key: PIG-1946
> URL: https://issues.apache.org/jira/browse/PIG-1946
> Project: Pig
>  Issue Type: Improvement
>Reporter: Bill Graham
>Assignee: Bill Graham
> Attachments: PIG-1946_1.patch
>
>
> Using {{HBaseStorage}} like so seems like a reasonable thing to do, but it 
> will yield unexpected results:
> {code}
> STORE result INTO 'hbase://foo' USING
>  org.apache.pig.backend.hadoop.hbase.HBaseStorage(
>  'info:first_name, info:last_name');
> {code}
> The problem us that a column named {{info:first_name,}} will be created, with 
> the trailing comma included. I've had numerous developers get tripped up on 
> this issue since everywhere else in Pig variables are separated by commas, so 
> I propose we fix it.
> I propose we trim leading/trailing commas from column names, but I'm open to 
> other ideas.
> Also should we accept column names that are comman-delimited without spaces?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (PIG-2021) Parser error while referring a map nested foreach

[Vivek Padmanabhan (JIRA)]

Parser error while referring a map nested foreach
-

 Key: PIG-2021
 URL: https://issues.apache.org/jira/browse/PIG-2021
 Project: Pig
  Issue Type: Bug
Affects Versions: 0.9.0
Reporter: Vivek Padmanabhan
 Fix For: 0.9.0


The below script is throwing parser errors
{code}
register string.jar;
A = load 'test1'  using MapLoader() as ( s, m, l );   
B = foreach A generate *, string.URLPARSE((chararray) s#'url') as parsedurl;
C = foreach B {
  urlpath = (chararray) parsedurl#'path';
  lc_urlpath = string.TOLOWERCASE((chararray) urlpath);
  generate *;
};
{code}

Error message;
| Failed to generate logical plan.
|Nested exception: org.apache.pig.impl.logicalLayer.FrontendException: ERROR 
2225: Projection with nothing to reference!



PIG-2002 reports a similar issue, but when i tried with the patch of PIG-2002 i 
was getting the below exception;
 ERROR org.apache.pig.tools.grunt.Grunt - ERROR 1200:   mismatched input '(' expecting SEMI_COLON


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (PIG-1989) complex type casting should return null on casting failure

[Daniel Dai (JIRA)]

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

Daniel Dai resolved PIG-1989.
-

  Resolution: Fixed
Hadoop Flags: [Reviewed]

Patch committed to both trunk and 0.9 branch.

> complex type casting should return null on casting failure 
> ---
>
> Key: PIG-1989
> URL: https://issues.apache.org/jira/browse/PIG-1989
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: Thejas M Nair
>Assignee: Daniel Dai
> Fix For: 0.9.0
>
> Attachments: PIG-1989-1.patch, PIG-1989-2.patch
>
>
> When casting fails for complex objects, pig is currently returning un-casted 
> object if the cast fails. 
> It should return null instead. That is consistent with the behavior when 
> casting to other basic types. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (PIG-1826) Unexpected data type -1 found in stream error

[Daniel Dai (JIRA)]

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

Daniel Dai resolved PIG-1826.
-

  Resolution: Fixed
Hadoop Flags: [Reviewed]

Patch committed to both trunk and 0.9 branch.

> Unexpected data type -1 found in stream error
> -
>
> Key: PIG-1826
> URL: https://issues.apache.org/jira/browse/PIG-1826
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.8.0
> Environment: This is pig 0.8.0 on a linux box
>Reporter: Jonathan Coveney
>Assignee: Daniel Dai
> Fix For: 0.9.0
>
> Attachments: PIG-1826-1.patch, PIG-1826.tar.gz, numgraph.java
>
>
> When running the attached udf I get the title error. By inserting printlns 
> extensively, the script is functioning properly and returning a DataBag, but 
> for whatever reason, pig does not detect it as such.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-1972) Cache split information details for data with large number of small part files

[Rajesh Balamohan (JIRA)]

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

Rajesh Balamohan commented on PIG-1972:
---

If the side data being read is small (ex:<= a block size), it would be 
replicated only in 3 nodes by default. So when every map is trying to read the 
side data, it would be choking to read the required details only from the 3 
nodes. Suggestion would be to increase the replication factor of the side data 
being read. Alternatively we can load the side data in the distributedcache as 
mentioned in this JIRA to reduce the performance impact.

> Cache split information details for data with large number of small part files
> --
>
> Key: PIG-1972
> URL: https://issues.apache.org/jira/browse/PIG-1972
> Project: Pig
>  Issue Type: Improvement
>  Components: impl
>Affects Versions: 0.8.0
> Environment: Pig 0.8 version with PigMix 
> http://wiki.apache.org/pig/PigMix
>Reporter: Rajesh Balamohan
>
> While running scalability benchmarks with Pig 0.8 & PigMix, L14 query listed 
> in http://wiki.apache.org/pig/PigMix showed no scalability characteristics 
> (i.e, for the same problem size response time should decrease as we increase 
> the number of nodes)
> Investigating further revealed that L14 query merge-joins small dataset and 
> another large dataset. If the small dataset has many part files with very 
> little amount of data, it causes a huge pressure on NameNode. This is because 
> it is read as a side file in all map slows.
> In the environment where I ran the experiment, small dataset was spread 
> across 1900+ part files in HDFS.
> Following codepath has the perf issue.
> DefaultIndexableLoader--> seekNear() --> initRightLoader() is causing the 
> huge delay. Since
> "users_sorted" data is spread across 1900+ small files, 
> FileInputFormat.getSplits() hits the namenode too
> frequently. 
> i.e, (number of machines * number of map slots * 1900+ times). This is the 
> reason why L14 is not scaling up.
> Suggestion would be to cache the splitInformation of the small dataset 
> instead of hitting the namenode too frequently.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-1994) e2e test harness deployment implementation for existing cluster

[Alan Gates (JIRA)]

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

Alan Gates updated PIG-1994:


Attachment: PIG-1994.patch

This provides a very basic ability to generate the data and place it both in an 
existing cluster and an existing postgres database.

> e2e test harness deployment implementation for existing cluster
> ---
>
> Key: PIG-1994
> URL: https://issues.apache.org/jira/browse/PIG-1994
> Project: Pig
>  Issue Type: Sub-task
>  Components: tools
>Reporter: Alan Gates
>Assignee: Alan Gates
> Fix For: 0.10
>
> Attachments: PIG-1994.patch
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-1994) e2e test harness deployment implementation for existing cluster

[Alan Gates (JIRA)]

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

Alan Gates updated PIG-1994:


Fix Version/s: 0.10
   Status: Patch Available  (was: Open)

> e2e test harness deployment implementation for existing cluster
> ---
>
> Key: PIG-1994
> URL: https://issues.apache.org/jira/browse/PIG-1994
> Project: Pig
>  Issue Type: Sub-task
>  Components: tools
>Reporter: Alan Gates
>Assignee: Alan Gates
> Fix For: 0.10
>
> Attachments: PIG-1994.patch
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-1989) complex type casting should return null on casting failure

[jirapos...@reviews.apache.org (JIRA)]

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

jirapos...@reviews.apache.org commented on PIG-1989:



---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/673/#review606
---

Ship it!


+1

- thejas


On 2011-04-28 20:56:30, Daniel Dai wrote:
bq.  
bq.  ---
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/673/
bq.  ---
bq.  
bq.  (Updated 2011-04-28 20:56:30)
bq.  
bq.  
bq.  Review request for pig and thejas.
bq.  
bq.  
bq.  Summary
bq.  ---
bq.  
bq.  See PIG-1989
bq.  
bq.  
bq.  This addresses bug PIG-1989.
bq.  https://issues.apache.org/jira/browse/PIG-1989
bq.  
bq.  
bq.  Diffs
bq.  -
bq.  
bq.
http://svn.apache.org/repos/asf/pig/trunk/src/org/apache/pig/backend/hadoop/executionengine/physicalLayer/expressionOperators/POCast.java
 1097304 
bq.
http://svn.apache.org/repos/asf/pig/trunk/test/org/apache/pig/test/TestPOCast.java
 1097304 
bq.  
bq.  Diff: https://reviews.apache.org/r/673/diff
bq.  
bq.  
bq.  Testing
bq.  ---
bq.  
bq.  Test-patch:
bq.   [exec] +1 overall.  
bq.   [exec] 
bq.   [exec] +1 @author.  The patch does not contain any @author tags.
bq.   [exec] 
bq.   [exec] +1 tests included.  The patch appears to include 3 new or 
modified tests.
bq.   [exec] 
bq.   [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
bq.   [exec] 
bq.   [exec] +1 javac.  The applied patch does not increase the total 
number of javac compiler warnings.
bq.   [exec] 
bq.   [exec] +1 findbugs.  The patch does not introduce any new 
Findbugs warnings.
bq.   [exec] 
bq.   [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
bq.  
bq.  Unit test:
bq.  all pass
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Daniel
bq.  
bq.



> complex type casting should return null on casting failure 
> ---
>
> Key: PIG-1989
> URL: https://issues.apache.org/jira/browse/PIG-1989
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: Thejas M Nair
>Assignee: Daniel Dai
> Fix For: 0.9.0
>
> Attachments: PIG-1989-1.patch, PIG-1989-2.patch
>
>
> When casting fails for complex objects, pig is currently returning un-casted 
> object if the cast fails. 
> It should return null instead. That is consistent with the behavior when 
> casting to other basic types. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Review Request: complex type casting should return null on casting failure

[thejas . nair]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/673/#review606
---

Ship it!


+1

- thejas


On 2011-04-28 20:56:30, Daniel Dai wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/673/
> ---
> 
> (Updated 2011-04-28 20:56:30)
> 
> 
> Review request for pig and thejas.
> 
> 
> Summary
> ---
> 
> See PIG-1989
> 
> 
> This addresses bug PIG-1989.
> https://issues.apache.org/jira/browse/PIG-1989
> 
> 
> Diffs
> -
> 
>   
> http://svn.apache.org/repos/asf/pig/trunk/src/org/apache/pig/backend/hadoop/executionengine/physicalLayer/expressionOperators/POCast.java
>  1097304 
>   
> http://svn.apache.org/repos/asf/pig/trunk/test/org/apache/pig/test/TestPOCast.java
>  1097304 
> 
> Diff: https://reviews.apache.org/r/673/diff
> 
> 
> Testing
> ---
> 
> Test-patch:
>  [exec] +1 overall.  
>  [exec] 
>  [exec] +1 @author.  The patch does not contain any @author tags.
>  [exec] 
>  [exec] +1 tests included.  The patch appears to include 3 new or 
> modified tests.
>  [exec] 
>  [exec] +1 javadoc.  The javadoc tool did not generate any warning 
> messages.
>  [exec] 
>  [exec] +1 javac.  The applied patch does not increase the total 
> number of javac compiler warnings.
>  [exec] 
>  [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
> warnings.
>  [exec] 
>  [exec] +1 release audit.  The applied patch does not increase the 
> total number of release audit warnings.
> 
> Unit test:
> all pass
> 
> 
> Thanks,
> 
> Daniel
> 
>

[jira] [Commented] (PIG-2015) Explain writes out logical plan twice

[Daniel Dai (JIRA)]

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

Daniel Dai commented on PIG-2015:
-

+1

> Explain writes out logical plan twice
> -
>
> Key: PIG-2015
> URL: https://issues.apache.org/jira/browse/PIG-2015
> Project: Pig
>  Issue Type: Bug
>  Components: impl
>Affects Versions: 0.9.0
>Reporter: Alan Gates
>Priority: Minor
> Fix For: 0.9.0
>
> Attachments: PIG-2015.patch
>
>
> Running explain on a script writes out the logical plan twice, the physical 
> plan once, and the map reduce plan once.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-2017) consumeMap() fails with EmptyStackException

[Daniel Dai (JIRA)]

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

Daniel Dai commented on PIG-2017:
-

+1, will commit if tests pass.

> consumeMap() fails with EmptyStackException
> ---
>
> Key: PIG-2017
> URL: https://issues.apache.org/jira/browse/PIG-2017
> Project: Pig
>  Issue Type: Bug
>Reporter: Jacob Perkins
> Attachments: utf8storagepatch.txt, utf8storagepatch_withtests.txt
>
>
> If a map is read in its serialized form, eg: [key#value], then the 
> consumeMap() method of Utf8StorageConverter fails for the following maps:
> {code:none}
> [a#)]
> [a#}]
> [a#"take a look at my lovely curly brace, }"]
> [a#'oh look, a closed parenthesis! )']
> {code}
> There are a couple of options:
> 1. Define an escape sequence (ie. quotes or a backslash)
> 2. Call it a bad record, go get a beer, and move on.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-1989) complex type casting should return null on casting failure

[jirapos...@reviews.apache.org (JIRA)]

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

jirapos...@reviews.apache.org commented on PIG-1989:



---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/673/
---

Review request for pig and thejas.


Summary
---

See PIG-1989


This addresses bug PIG-1989.
https://issues.apache.org/jira/browse/PIG-1989


Diffs
-

  
http://svn.apache.org/repos/asf/pig/trunk/src/org/apache/pig/backend/hadoop/executionengine/physicalLayer/expressionOperators/POCast.java
 1097304 
  
http://svn.apache.org/repos/asf/pig/trunk/test/org/apache/pig/test/TestPOCast.java
 1097304 

Diff: https://reviews.apache.org/r/673/diff


Testing
---

Test-patch:
 [exec] +1 overall.  
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 3 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.

Unit test:
all pass


Thanks,

Daniel



> complex type casting should return null on casting failure 
> ---
>
> Key: PIG-1989
> URL: https://issues.apache.org/jira/browse/PIG-1989
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: Thejas M Nair
>Assignee: Daniel Dai
> Fix For: 0.9.0
>
> Attachments: PIG-1989-1.patch, PIG-1989-2.patch
>
>
> When casting fails for complex objects, pig is currently returning un-casted 
> object if the cast fails. 
> It should return null instead. That is consistent with the behavior when 
> casting to other basic types. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Review Request: complex type casting should return null on casting failure

[Daniel Dai]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/673/
---

Review request for pig and thejas.


Summary
---

See PIG-1989


This addresses bug PIG-1989.
https://issues.apache.org/jira/browse/PIG-1989


Diffs
-

  
http://svn.apache.org/repos/asf/pig/trunk/src/org/apache/pig/backend/hadoop/executionengine/physicalLayer/expressionOperators/POCast.java
 1097304 
  
http://svn.apache.org/repos/asf/pig/trunk/test/org/apache/pig/test/TestPOCast.java
 1097304 

Diff: https://reviews.apache.org/r/673/diff


Testing
---

Test-patch:
 [exec] +1 overall.  
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 3 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.

Unit test:
all pass


Thanks,

Daniel

[jira] [Updated] (PIG-1989) complex type casting should return null on casting failure

[Daniel Dai (JIRA)]

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

Daniel Dai updated PIG-1989:


Attachment: PIG-1989-2.patch

PIG-1989-2.patch include suggestions from Thejas, and address findbug warnings.

> complex type casting should return null on casting failure 
> ---
>
> Key: PIG-1989
> URL: https://issues.apache.org/jira/browse/PIG-1989
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: Thejas M Nair
>Assignee: Daniel Dai
> Fix For: 0.9.0
>
> Attachments: PIG-1989-1.patch, PIG-1989-2.patch
>
>
> When casting fails for complex objects, pig is currently returning un-casted 
> object if the cast fails. 
> It should return null instead. That is consistent with the behavior when 
> casting to other basic types. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-2012) Comments at the begining of the file throws off line numbers in errors

[Richard Ding (JIRA)]

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

Richard Ding updated PIG-2012:
--

Attachment: PIG-2012_1.patch

> Comments at the begining of the file throws off line numbers in errors
> --
>
> Key: PIG-2012
> URL: https://issues.apache.org/jira/browse/PIG-2012
> Project: Pig
>  Issue Type: Bug
>  Components: impl
>Affects Versions: 0.9.0
>Reporter: Alan Gates
>Assignee: Richard Ding
> Fix For: 0.9.0
>
> Attachments: PIG-2012_1.patch, macro.pig
>
>
> The preprocessor does not appear to be handling leading comments properly 
> when calculating line numbers for error messages.  In the attached script, 
> the error is reported to be on line 7.  It is actually on line 10.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-2015) Explain writes out logical plan twice

[Alan Gates (JIRA)]

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

Alan Gates commented on PIG-2015:
-

Unit tests pass.  Since I just removed one line I'm not going to bother running 
test-patch.sh

> Explain writes out logical plan twice
> -
>
> Key: PIG-2015
> URL: https://issues.apache.org/jira/browse/PIG-2015
> Project: Pig
>  Issue Type: Bug
>  Components: impl
>Affects Versions: 0.9.0
>Reporter: Alan Gates
>Priority: Minor
> Fix For: 0.9.0
>
> Attachments: PIG-2015.patch
>
>
> Running explain on a script writes out the logical plan twice, the physical 
> plan once, and the map reduce plan once.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: The Git Repository

[Dmitriy Ryaboy]

Yes, if you are looking at git.apache.org

D

On Thu, Apr 28, 2011 at 8:42 AM, Zhijie Shen  wrote:

> Hi Developers,
>
> I plan to work on the Pig project with git because I think it is more
> flexible for me to manage my own modifications on the code. But before
> that,
> I wanna make sure that the git repository will keep up-to-date with the
> main
> svn repository, right?
>
> Regards,
> Zhijie
>
> --
> Zhijie Shen
> School of Computing
> National University of Singapore
> 
>

[jira] [Created] (PIG-2020) Valid query fails to validate

[Xuefu Zhang (JIRA)]

Valid query fails to validate
-

 Key: PIG-2020
 URL: https://issues.apache.org/jira/browse/PIG-2020
 Project: Pig
  Issue Type: Bug
Affects Versions: 0.8.0, 0.9.0
Reporter: Xuefu Zhang
Assignee: Xuefu Zhang
 Fix For: 0.9.0


The following query seems valid:

A = load 'x';
B = foreach A { T = filter $0 by $1 > $2; generate T; };
Store B into 'y';

However, the query fails due to validation error in 0.8:

2011-04-28 09:08:06,846 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
1026: Attempt to fetch field 1 from schema of size 1

Similar error is given in 0.9.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

The Git Repository

[Zhijie Shen]

Hi Developers,

I plan to work on the Pig project with git because I think it is more
flexible for me to manage my own modifications on the code. But before that,
I wanna make sure that the git repository will keep up-to-date with the main
svn repository, right?

Regards,
Zhijie

-- 
Zhijie Shen
School of Computing
National University of Singapore

[jira] [Updated] (PIG-2019) smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of test classes

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated PIG-2019:


  Component/s: build
Affects Version/s: 0.9.0

> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of 
> test classes
> 
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
>  Issue Type: Bug
>  Components: build
>Affects Versions: 0.9.0
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
> Attachments: PIG-2019.patch
>
>
> pigsmoke artifact uses classes from pigunit for real cluster testing. 
> However, in the deployment phase the artifact comes out without the classes 
> added. It happens because of the execution order of targets during deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work started] (PIG-2019) smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of test classes

[Konstantin Boudnik (JIRA)]

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

Work on PIG-2019 started by Konstantin Boudnik.

> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of 
> test classes
> 
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
>  Issue Type: Bug
>  Components: build
>Affects Versions: 0.9.0
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
> Attachments: PIG-2019.patch
>
>
> pigsmoke artifact uses classes from pigunit for real cluster testing. 
> However, in the deployment phase the artifact comes out without the classes 
> added. It happens because of the execution order of targets during deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-2019) smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of test classes

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated PIG-2019:


Fix Version/s: 0.9.0
   Status: Patch Available  (was: In Progress)

> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of 
> test classes
> 
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
>  Issue Type: Bug
>  Components: build
>Affects Versions: 0.9.0
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
> Attachments: PIG-2019.patch
>
>
> pigsmoke artifact uses classes from pigunit for real cluster testing. 
> However, in the deployment phase the artifact comes out without the classes 
> added. It happens because of the execution order of targets during deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PIG-2019) smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of test classes

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on PIG-2019:
-

The easiest way to guarantee the presence of the compiled classes is to add a 
dependency to smoketests-jar target (see the patch).

> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of 
> test classes
> 
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
>  Issue Type: Bug
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Attachments: PIG-2019.patch
>
>
> pigsmoke artifact uses classes from pigunit for real cluster testing. 
> However, in the deployment phase the artifact comes out without the classes 
> added. It happens because of the execution order of targets during deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-2019) smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of test classes

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated PIG-2019:


Attachment: PIG-2019.patch

> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of 
> test classes
> 
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
>  Issue Type: Bug
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Attachments: PIG-2019.patch
>
>
> pigsmoke artifact uses classes from pigunit for real cluster testing. 
> However, in the deployment phase the artifact comes out without the classes 
> added. It happens because of the execution order of targets during deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PIG-2019) smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of test classes

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated PIG-2019:


Description: pigsmoke artifact uses classes from pigunit for real cluster 
testing. However, in the deployment phase the artifact comes out without the 
classes added. It happens because of the execution order of targets during 
deployment.
   Assignee: Konstantin Boudnik
Summary: smoketest-jar target has to depend on pigunit-jar to guarantee 
inclusion of test classes  (was: smoketest-ar)

> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of 
> test classes
> 
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
>  Issue Type: Bug
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
>
> pigsmoke artifact uses classes from pigunit for real cluster testing. 
> However, in the deployment phase the artifact comes out without the classes 
> added. It happens because of the execution order of targets during deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (PIG-2019) smoketest-ar

[Konstantin Boudnik (JIRA)]

smoketest-ar


 Key: PIG-2019
 URL: https://issues.apache.org/jira/browse/PIG-2019
 Project: Pig
  Issue Type: Bug
Reporter: Konstantin Boudnik




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira