[jira] Subscription: PIG patch available

2013-05-07 Thread jira
Issue Subscription
Filter: PIG patch available (22 issues)

Subscriber: pigdaily

Key Summary
PIG-3297Avro files with stringType set to String cannot be read by the 
AvroStorage LoadFunc
https://issues.apache.org/jira/browse/PIG-3297
PIG-3295Casting from bytearray failing after Union (even when each field is 
from a single Loader)
https://issues.apache.org/jira/browse/PIG-3295
PIG-3291TestExampleGenerator fails on Windows because of lack of file name 
escaping
https://issues.apache.org/jira/browse/PIG-3291
PIG-3285Jobs using HBaseStorage fail to ship dependency jars
https://issues.apache.org/jira/browse/PIG-3285
PIG-3258Patch to allow MultiStorage to use more than one index to generate 
output tree
https://issues.apache.org/jira/browse/PIG-3258
PIG-3257Add unique identifier UDF
https://issues.apache.org/jira/browse/PIG-3257
PIG-3247Piggybank functions to mimic OVER clause in SQL
https://issues.apache.org/jira/browse/PIG-3247
PIG-3210Pig fails to start when it cannot write log to log files
https://issues.apache.org/jira/browse/PIG-3210
PIG-3199Expose LogicalPlan via PigServer API
https://issues.apache.org/jira/browse/PIG-3199
PIG-3166Update eclipse .classpath according to ivy library.properties
https://issues.apache.org/jira/browse/PIG-3166
PIG-3123Simplify Logical Plans By Removing Unneccessary Identity Projections
https://issues.apache.org/jira/browse/PIG-3123
PIG-3088Add a builtin udf which removes prefixes
https://issues.apache.org/jira/browse/PIG-3088
PIG-3069Native Windows Compatibility for Pig E2E Tests and Harness
https://issues.apache.org/jira/browse/PIG-3069
PIG-3026Pig checked-in baseline comparisons need a pre-filter to address 
OS-specific newline differences
https://issues.apache.org/jira/browse/PIG-3026
PIG-3025TestPruneColumn unit test - SimpleEchoStreamingCommand perl inline 
script needs simplification
https://issues.apache.org/jira/browse/PIG-3025
PIG-3024TestEmptyInputDir unit test - hadoop version detection logic is 
brittle
https://issues.apache.org/jira/browse/PIG-3024
PIG-3015Rewrite of AvroStorage
https://issues.apache.org/jira/browse/PIG-3015
PIG-2959Add a pig.cmd for Pig to run under Windows
https://issues.apache.org/jira/browse/PIG-2959
PIG-2955 Fix bunch of Pig e2e tests on Windows 
https://issues.apache.org/jira/browse/PIG-2955
PIG-2248Pig parser does not detect when a macro name masks a UDF name
https://issues.apache.org/jira/browse/PIG-2248
PIG-2244Macros cannot be passed relation names
https://issues.apache.org/jira/browse/PIG-2244
PIG-1914Support load/store JSON data in Pig
https://issues.apache.org/jira/browse/PIG-1914

You may edit this subscription at:
https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13225&filterId=12322384


[jira] [Commented] (PIG-3315) Automaton dependency missing from Pig 11.1-h2 POM.

2013-05-07 Thread Steve Loughran (JIRA)

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

Steve Loughran commented on PIG-3315:
-

Workaround is for downstream projects to declare the dependency explicitly
{code}
 
  dk.brics.automaton
  automaton
  1.11-8

 {code}

> Automaton dependency missing from Pig 11.1-h2 POM.
> --
>
> Key: PIG-3315
> URL: https://issues.apache.org/jira/browse/PIG-3315
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.11.1
> Environment: Pig 11.1-h2
>Reporter: Steve Loughran
>Priority: Minor
>
> The automaton dependency is missing from pig-11.1-h2 POM, leading to a stack 
> trace starting with {{java.lang.NoClassDefFoundError: 
> dk/brics/automaton/Automaton}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (PIG-3315) Automaton dependency missing from Pig 11.1-h2 POM.

2013-05-07 Thread Steve Loughran (JIRA)

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

Steve Loughran commented on PIG-3315:
-

Full stack]{code}
java.lang.NoClassDefFoundError: dk/brics/automaton/Automaton
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at 
org.apache.pig.impl.util.JarManager$DefaultPigPackages.(JarManager.java:99)
at org.apache.pig.impl.util.JarManager.createJar(JarManager.java:136)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.JobControlCompiler.getJob(JobControlCompiler.java:517)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.JobControlCompiler.compile(JobControlCompiler.java:294)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher.launchPig(MapReduceLauncher.java:177)
at org.apache.pig.PigServer.launchPlan(PigServer.java:1264)
at 
org.apache.pig.PigServer.executeCompiledLogicalPlan(PigServer.java:1249)
at org.apache.pig.PigServer.storeEx(PigServer.java:931)
at org.apache.pig.PigServer.store(PigServer.java:898)
at org.apache.pig.PigServer.openIterator(PigServer.java:811)
at org.apache.pig.PigServer$openIterator.call(Unknown Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at 
org.apache.hadoop.fs.swift.integration.IntegrationTestBase.runBasePigJob(IntegrationTestBase.groovy:257)
at 
org.apache.hadoop.fs.swift.integration.IntegrationTestBase$runBasePigJob.callCurrent(Unknown
 Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at 
org.apache.hadoop.fs.swift.integration.pig.TestPig.testLoadGeneratedData(TestPig.groovy:37)
{code}

> Automaton dependency missing from Pig 11.1-h2 POM.
> --
>
> Key: PIG-3315
> URL: https://issues.apache.org/jira/browse/PIG-3315
> Project: Pig
>  Issue Type: Bug
>Affects Versions: 0.11.1
> Environment: Pig 11.1-h2
>Reporter: Steve Loughran
>Priority: Minor
>
> The automaton dependency is missing from pig-11.1-h2 POM, leading to a stack 
> trace starting with {{java.lang.NoClassDefFoundError: 
> dk/brics/automaton/Automaton}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (PIG-3315) Automaton dependency missing from Pig 11.1-h2 POM.

2013-05-07 Thread Steve Loughran (JIRA)
Steve Loughran created PIG-3315:
---

 Summary: Automaton dependency missing from Pig 11.1-h2 POM.
 Key: PIG-3315
 URL: https://issues.apache.org/jira/browse/PIG-3315
 Project: Pig
  Issue Type: Bug
Affects Versions: 0.11.1
 Environment: Pig 11.1-h2
Reporter: Steve Loughran
Priority: Minor


The automaton dependency is missing from pig-11.1-h2 POM, leading to a stack 
trace starting with {{java.lang.NoClassDefFoundError: 
dk/brics/automaton/Automaton}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (PIG-3313) pig job hang if the job tracker is bounced during execution

2013-05-07 Thread Chenjie Yu (JIRA)

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

Chenjie Yu updated PIG-3313:


Attachment: PIG-3313

The patch that should fix this problem. Tested ok.

> pig job hang if the job tracker is bounced during execution
> ---
>
> Key: PIG-3313
> URL: https://issues.apache.org/jira/browse/PIG-3313
> Project: Pig
>  Issue Type: Bug
>Reporter: Chenjie Yu
> Attachments: PIG-3313
>
>
> When running a pig job through PigRunner, after the mapreduce job is 
> submitted, if there is a job tracker bounce which doesn't get back up very 
> soon, the pig job will hang there.
> The reason is pig is keeping all the JobControl objects, which are non-deamon 
> threads, that keeps connecting to jobtracker. If the job tracker is down, pig 
> will fail, but those jobcontrol threads keep running and there is no one who 
> can stop them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (PIG-3307) Refactor physical operators to remove methods parameters that are always null

2013-05-07 Thread Julien Le Dem (JIRA)

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

Julien Le Dem commented on PIG-3307:


[~daijy]what's the recommended approach? If you have a setup to do perf test 
that would be helpful.


> Refactor physical operators to remove methods parameters that are always null
> -
>
> Key: PIG-3307
> URL: https://issues.apache.org/jira/browse/PIG-3307
> Project: Pig
>  Issue Type: Improvement
>Reporter: Julien Le Dem
>Assignee: Julien Le Dem
> Attachments: PIG-3307_0.patch, PIG-3307_1.patch, PIG-3307_2.patch
>
>
> The physical operators are sometimes overly complex. I'm trying to cleanup 
> some unnecessary code.
> in particular there is an array of getNext(*T* v) where the value v does not 
> seem to have any importance and is just used to pick the correct method.
> I have started a refactoring for a more readable getNext*T*().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (PIG-3314) make better symbol resolving order in Pig

2013-05-07 Thread Johnny Zhang (JIRA)

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

Johnny Zhang updated PIG-3314:
--

Description: 
this idea comes when we trying to resolve PIG-2248, please take a look the 
comments starts from 
https://issues.apache.org/jira/browse/PIG-2248?focusedCommentId=13648831&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13648831

Basically, we want sure different level of symbol in Pig, when they have name 
conflict, higher side symbol can mask lover side symbol.

We want first make an agreement on the symbol, then we are going to
(1) add unit tests to make sure it is working as expected, otherwise, open jira 
and fix it
(2) document the usage

  was:
this idea comes when we trying to resolve PIG-2248, please take a look the 
comments starts from 
https://issues.apache.org/jira/browse/PIG-2248?focusedCommentId=13648831&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13648831

Basically, we want sure different level of symbol in Pig, when they have name 
conflict, higher side symbol can mask lover side symbol.


> make better symbol resolving order in Pig
> -
>
> Key: PIG-3314
> URL: https://issues.apache.org/jira/browse/PIG-3314
> Project: Pig
>  Issue Type: Improvement
>  Components: grunt, parser
>Reporter: Johnny Zhang
>
> this idea comes when we trying to resolve PIG-2248, please take a look the 
> comments starts from 
> https://issues.apache.org/jira/browse/PIG-2248?focusedCommentId=13648831&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13648831
> Basically, we want sure different level of symbol in Pig, when they have name 
> conflict, higher side symbol can mask lover side symbol.
> We want first make an agreement on the symbol, then we are going to
> (1) add unit tests to make sure it is working as expected, otherwise, open 
> jira and fix it
> (2) document the usage

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (PIG-3314) make better symbol resolving order in Pig

2013-05-07 Thread Johnny Zhang (JIRA)
Johnny Zhang created PIG-3314:
-

 Summary: make better symbol resolving order in Pig
 Key: PIG-3314
 URL: https://issues.apache.org/jira/browse/PIG-3314
 Project: Pig
  Issue Type: Improvement
  Components: grunt, parser
Reporter: Johnny Zhang


this idea comes when we trying to resolve PIG-2248, please take a look the 
comments starts from 
https://issues.apache.org/jira/browse/PIG-2248?focusedCommentId=13648831&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13648831

Basically, we want sure different level of symbol in Pig, when they have name 
conflict, higher side symbol can mask lover side symbol.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira