You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ashish Thusoo (JIRA)" <ji...@apache.org> on 2008/11/21 05:14:44 UTC
[jira] Created: (HIVE-76) Column number mismatch between query and
destination tables when alias.* expressions are present in the select list
of a join
Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
-----------------------------------------------------------------------------------------------------------------------------
Key: HIVE-76
URL: https://issues.apache.org/jira/browse/HIVE-76
Project: Hadoop Hive
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Ashish Thusoo
Assignee: Ashish Thusoo
Fix For: 0.20.0
Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-76) Column number mismatch between query
and destination tables when alias.* expressions are present in the select
list of a join
Posted by "Ashish Thusoo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649591#action_12649591 ]
Ashish Thusoo commented on HIVE-76:
-----------------------------------
The following test case leads to the error:
CREATE TABLE dest1(key1 INT, value1 STRING, key2 INT, value2 STRING) STORED AS TEXTFILE;
FROM src src1 JOIN src src2 ON (src1.key = src2.key)
INSERT OVERWRITE TABLE dest1 SELECT src1.*, src2.*;
where src has two columns (key INT, value STRING)
In this situation we should not be getting a column mismatch error as the destination has 4 columns and SELECT src1.*, src2.* also should
have 4 columns. However, due to a bug in SemanticAnalyzer we add all the columns in the select list to the row resolver as many times as an
expression of the form alias.* appears.
As a result it is impossible to insert into a destination table. A workaround is to enumerate all the columns and not use alias.* in the select list
with joins when inserting the results into a table.
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-76) Column number mismatch between query and
destination tables when alias.* expressions are present in the select list
of a join
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-76:
-------------------------------
Fix Version/s: 0.3.0
(was: 0.6.0)
Component/s: Query Processor
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.3.0
>
> Attachments: patch-76.txt, patch-76_1.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-76) Column number mismatch between query and
destination tables when alias.* expressions are present in the select list
of a join
Posted by "Ashish Thusoo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Thusoo updated HIVE-76:
------------------------------
Attachment: patch-76_1.txt
New patch which also fixes join10.q
Note that join10.q was already broken before.
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
> Attachments: patch-76.txt, patch-76_1.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-76) Column number mismatch between query
and destination tables when alias.* expressions are present in the select
list of a join
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649708#action_12649708 ]
Namit Jain commented on HIVE-76:
--------------------------------
can you add a select also in join10.q.
I mean select without the explain also, like all other tests
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
> Attachments: patch-76.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-76) Column number mismatch between query
and destination tables when alias.* expressions are present in the select
list of a join
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649819#action_12649819 ]
Namit Jain commented on HIVE-76:
--------------------------------
+1
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
> Attachments: patch-76.txt, patch-76_1.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-76) Column number mismatch between query and
destination tables when alias.* expressions are present in the select list
of a join
Posted by "Ashish Thusoo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Thusoo updated HIVE-76:
------------------------------
Attachment: patch-76.txt
Fix for the bug and test case.
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
> Attachments: patch-76.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-76) Column number mismatch between query and
destination tables when alias.* expressions are present in the select list
of a join
Posted by "Ashish Thusoo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Thusoo updated HIVE-76:
------------------------------
Status: Patch Available (was: Open)
submitted patch.
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
> Attachments: patch-76.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-76) Column number mismatch between query and
destination tables when alias.* expressions are present in the select list
of a join
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HIVE-76:
---------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks Ashish!
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-76
> URL: https://issues.apache.org/jira/browse/HIVE-76
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Ashish Thusoo
> Assignee: Ashish Thusoo
> Fix For: 0.20.0
>
> Attachments: patch-76.txt, patch-76_1.txt
>
>
> Column number mismatch between query and destination tables when alias.* expressions are present in the select list of a join. The reason is due to a bug in how the row resolver is constructed in SemanticAnalyzer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.