You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (JIRA)" <ji...@apache.org> on 2009/03/16 19:01:50 UTC
[jira] Created: (HIVE-350) [Hive] wrong order in explain plan
[Hive] wrong order in explain plan
----------------------------------
Key: HIVE-350
URL: https://issues.apache.org/jira/browse/HIVE-350
Project: Hadoop Hive
Issue Type: Bug
Components: Query Processor
Reporter: Namit Jain
Assignee: Namit Jain
In case of multiple aggregations, the explain plan might be wrong -the order of aggregations since AbParseInfo maintains the information in a hashmap, which does the guarantee the results to be returned in order
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-350) [Hive] wrong order in explain plan
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-350:
----------------------------
Resolution: Fixed
Fix Version/s: 0.3.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
committed.
> [Hive] wrong order in explain plan
> ----------------------------------
>
> Key: HIVE-350
> URL: https://issues.apache.org/jira/browse/HIVE-350
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Fix For: 0.3.0
>
> Attachments: hive.350.1.patch
>
>
> In case of multiple aggregations, the explain plan might be wrong -the order of aggregations since AbParseInfo maintains the information in a hashmap, which does the guarantee the results to be returned in order
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-350) [Hive] wrong order in explain plan
Posted by "Ashish Thusoo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683200#action_12683200 ]
Ashish Thusoo commented on HIVE-350:
------------------------------------
+1.
Looks good to me.
> [Hive] wrong order in explain plan
> ----------------------------------
>
> Key: HIVE-350
> URL: https://issues.apache.org/jira/browse/HIVE-350
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: hive.350.1.patch
>
>
> In case of multiple aggregations, the explain plan might be wrong -the order of aggregations since AbParseInfo maintains the information in a hashmap, which does the guarantee the results to be returned in order
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-350) [Hive] wrong order in explain plan
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682816#action_12682816 ]
Namit Jain commented on HIVE-350:
---------------------------------
The explain plan is not wrong perse - the order is random, and eventually the select corrects the order. But, it was very difficult to understand
> [Hive] wrong order in explain plan
> ----------------------------------
>
> Key: HIVE-350
> URL: https://issues.apache.org/jira/browse/HIVE-350
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: hive.350.1.patch
>
>
> In case of multiple aggregations, the explain plan might be wrong -the order of aggregations since AbParseInfo maintains the information in a hashmap, which does the guarantee the results to be returned in order
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-350) [Hive] wrong order in explain plan
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-350:
----------------------------
Status: Patch Available (was: Open)
> [Hive] wrong order in explain plan
> ----------------------------------
>
> Key: HIVE-350
> URL: https://issues.apache.org/jira/browse/HIVE-350
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: hive.350.1.patch
>
>
> In case of multiple aggregations, the explain plan might be wrong -the order of aggregations since AbParseInfo maintains the information in a hashmap, which does the guarantee the results to be returned in order
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-350) [Hive] wrong order in explain plan
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-350:
----------------------------
Attachment: hive.350.1.patch
> [Hive] wrong order in explain plan
> ----------------------------------
>
> Key: HIVE-350
> URL: https://issues.apache.org/jira/browse/HIVE-350
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: hive.350.1.patch
>
>
> In case of multiple aggregations, the explain plan might be wrong -the order of aggregations since AbParseInfo maintains the information in a hashmap, which does the guarantee the results to be returned in order
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.