[jira] Commented: (PIG-1695) MergeForEach does not carry user defined schema if any one of the merged ForEach has user defined schema

[ https://issues.apache.org/jira/browse/PIG-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926495#action_12926495 ] Thejas M Nair commented on PIG-1695: +1 With this fix, pig does not merge the foreach st

Build failed in Hudson: Pig-trunk #854

See Changes: [hashutosh] PIG-1696: Performance: Use System.arraycopy() instead of manually copying the bytes while reading the data -- [...truncated 2535 lines...] [ivy:resolve] found commons-

Build failed in Hudson: Pig-trunk-commit #576

See Changes: [thejas] PIG-1684: Inconsistent usage of store func. -- [...truncated 4985 lines...] [ivy:resolve] found org.apache.hadoop#hadoop-core;0.20.2 in maven2 [ivy:resolve] found

[jira] Updated: (PIG-1704) Output Compression is not at work if the output path is absolute and there is a trailing / afte the compression suffix

[ https://issues.apache.org/jira/browse/PIG-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Zhou updated PIG-1704: -- Attachment: PIG-1704.patch > Output Compression is not at work if the output path is absolute and there is > a t

[jira] Created: (PIG-1704) Output Compression is not at work if the output path is absolute and there is a trailing / afte the compression suffix

Output Compression is not at work if the output path is absolute and there is a trailing / afte the compression suffix -- Key: PIG-1704 URL: https:

Build failed in Hudson: Pig-trunk #853

See Changes: [thejas] PIG-1684: Inconsistent usage of store func. [thejas] PIG-1618: Switch to new parser generator technology (xuefuz via thejas) -- [...truncated 2525 lines...] [ivy:resolve]

Build failed in Hudson: Pig-trunk-commit #577

See Changes: [hashutosh] PIG-1696: Performance: Use System.arraycopy() instead of manually copying the bytes while reading the data -- [...truncated 4975 lines...] [ivy:resolve] found o

Re: Understanding Logical Plan

Currently parsing and logical plan building is mixed. So, as script is getting parsed, its corresponding logical plan is built. So, at the end of parsing phase, a logical plan is emitted. Inner plans are also built at the same time. The whole plan construction is done in once shot. This plan is the

[jira] Commented: (PIG-480) PERFORMANCE: Use identity mapper in a chain of M-R jobs

[ https://issues.apache.org/jira/browse/PIG-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926312#action_12926312 ] Thejas M Nair commented on PIG-480: --- Note that the identity map proposed in this jira is use

[jira] Commented: (PIG-480) PERFORMANCE: Use identity mapper in a chain of M-R jobs

[ https://issues.apache.org/jira/browse/PIG-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926310#action_12926310 ] Thejas M Nair commented on PIG-480: --- In the use case example given in description, only one

[jira] Updated: (PIG-1696) Performance: Use System.arraycopy() instead of manually copying the bytes while reading the data

[ https://issues.apache.org/jira/browse/PIG-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated PIG-1696: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk. > P