You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Richard Ding (JIRA)" <ji...@apache.org> on 2010/02/27 02:38:05 UTC
[jira] Created: (PIG-1267) Problems with partition filter optimizer
Problems with partition filter optimizer
----------------------------------------
Key: PIG-1267
URL: https://issues.apache.org/jira/browse/PIG-1267
Project: Pig
Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Richard Ding
Assignee: Richard Ding
There are a couple of problems with the current partition filter optimizer:
1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1267) Problems with partition filter
optimizer
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840033#action_12840033 ]
Daniel Dai commented on PIG-1267:
---------------------------------
+1 for commit.
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1267.patch
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1267) Problems with partition filter optimizer
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Ding updated PIG-1267:
------------------------------
Status: Patch Available (was: Open)
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1267.patch
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1267) Problems with partition filter optimizer
Posted by "Olga Natkovich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Natkovich updated PIG-1267:
--------------------------------
Fix Version/s: 0.7.0
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1267) Problems with partition filter
optimizer
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840007#action_12840007 ]
Hadoop QA commented on PIG-1267:
--------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12437539/PIG-1267.patch
against trunk revision 916793.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/231/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/231/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/231/console
This message is automatically generated.
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1267.patch
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1267) Problems with partition filter optimizer
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Ding updated PIG-1267:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1267.patch
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (PIG-1267) Problems with partition filter optimizer
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dai closed PIG-1267.
---------------------------
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1267.patch
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1267) Problems with partition filter optimizer
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Ding updated PIG-1267:
------------------------------
Attachment: PIG-1267.patch
> Problems with partition filter optimizer
> ----------------------------------------
>
> Key: PIG-1267
> URL: https://issues.apache.org/jira/browse/PIG-1267
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1267.patch
>
>
> There are a couple of problems with the current partition filter optimizer:
> 1. When a partition filter is removed from the logical plan, the input index of the following join/cogroup operator may change, which in turn changes the ordering of the fields in the schema and results in compile-time errors.
> 2. At most one partition filter can be removed per plan, while multiple partition filters can exist in the cases of joins.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.