[jira] Updated: (PIG-835) Multiquery optimization does not handle the case where the map keys in the split plans have different key types (tuple and non tuple key type)

[ https://issues.apache.org/jira/browse/PIG-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-835: --- Status: Open (was: Patch Available) > Multiquery optimization does not handle the case where the map ke

[jira] Updated: (PIG-835) Multiquery optimization does not handle the case where the map keys in the split plans have different key types (tuple and non tuple key type)

[ https://issues.apache.org/jira/browse/PIG-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-835: --- Status: Patch Available (was: Open) > Multiquery optimization does not handle the case where the map ke

[jira] Created: (PIG-838) Parser does not handle ctrl-m ('\u000d') as argument to PigStorage

Parser does not handle ctrl-m ('\u000d') as argument to PigStorage -- Key: PIG-838 URL: https://issues.apache.org/jira/browse/PIG-838 Project: Pig Issue Type: Bug Affects Ve

[jira] Commented: (PIG-838) Parser does not handle ctrl-m ('\u000d') as argument to PigStorage

[ https://issues.apache.org/jira/browse/PIG-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716769#action_12716769 ] Pradeep Kamath commented on PIG-838: THe issue might be because we have in QueryParser.jjt

[jira] Updated: (PIG-830) Port Apache Log parsing piggybank contrib to Pig 0.2

[ https://issues.apache.org/jira/browse/PIG-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-830: --- Resolution: Fixed Fix Version/s: 0.3.0 Status: Resolved (was: Patch Available) Patch checked

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

[ https://issues.apache.org/jira/browse/PIG-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716757#action_12716757 ] Hadoop QA commented on PIG-765: --- -1 overall. Here are the results of testing the latest attachm

Build failed in Hudson: Pig-Patch-minerva.apache.org #73

See http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/73/changes Changes: [olga] missing doc file [gates] PIG-831: Turned off reporting of records and bytes written for mutli-store queries as the returned results are confusing and wrong. --

[jira] Commented: (PIG-823) Hadoop Metadata Service

[ https://issues.apache.org/jira/browse/PIG-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716722#action_12716722 ] Jeff Hammerbacher commented on PIG-823: --- Hey Alan, Thanks for the additional detail. I

[jira] Resolved: (PIG-837) docs ant target is broken

[ https://issues.apache.org/jira/browse/PIG-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olga Natkovich resolved PIG-837. Resolution: Fixed committed missing file > docs ant target is broken > -- >

[jira] Updated: (PIG-835) Multiquery optimization does not handle the case where the map keys in the split plans have different key types (tuple and non tuple key type)

[ https://issues.apache.org/jira/browse/PIG-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-835: --- Attachment: PIG-835.patch The root cause of the issue is that the current multiQueryOptimizer checks if

[jira] Updated: (PIG-835) Multiquery optimization does not handle the case where the map keys in the split plans have different key types (tuple and non tuple key type)

[ https://issues.apache.org/jira/browse/PIG-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Kamath updated PIG-835: --- Status: Patch Available (was: Open) > Multiquery optimization does not handle the case where the map ke

[jira] Commented: (PIG-823) Hadoop Metadata Service

[ https://issues.apache.org/jira/browse/PIG-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716679#action_12716679 ] Alan Gates commented on PIG-823: By lower level of metadata, we don't mean storing information

[jira] Commented: (PIG-830) Port Apache Log parsing piggybank contrib to Pig 0.2

[ https://issues.apache.org/jira/browse/PIG-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716677#action_12716677 ] Alan Gates commented on PIG-830: I've started reviewing it. I hope to finish the review today

[jira] Commented: (PIG-830) Port Apache Log parsing piggybank contrib to Pig 0.2

[ https://issues.apache.org/jira/browse/PIG-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716667#action_12716667 ] Dmitriy V. Ryaboy commented on PIG-830: --- Pig commiters, could you review the latest when

[jira] Commented: (PIG-833) Storage access layer

[ https://issues.apache.org/jira/browse/PIG-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716578#action_12716578 ] Hong Tang commented on PIG-833: --- @Jeff, I might have read a bit too much into the lines. I was r