hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghotham Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-132) Show table and describe results should be read via FetchTask
Date Mon, 05 Jan 2009 18:39:44 GMT

    [ https://issues.apache.org/jira/browse/HIVE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660848#action_12660848
] 

Raghotham Murthy commented on HIVE-132:
---------------------------------------

The table Information is actually another row with the same schema: column-name = "Table Information",
column-type = <the extended information>, column-description = null. Without this, its
not possible to use the FetchTask to get to the extended data. I also added an additional
empty row (all columns are null). I could hack it such that that a ':' is printed after "Table
Information" and write out the actual information in another row. But I cant get rid of the
extra tab since I have to print all rows using the same schema. I think its better to figure
out a schema for the extended information rather than hacking this more to make it look better
in unstructured form.

DDLSemanticAnalyzer: when i set the null string to empty string '\N' was being displayed.
So, I set it to space instead. I was not sure what to change to make empty string work.

> Show table and describe results should be read via FetchTask
> ------------------------------------------------------------
>
>                 Key: HIVE-132
>                 URL: https://issues.apache.org/jira/browse/HIVE-132
>             Project: Hadoop Hive
>          Issue Type: New Feature
>          Components: Query Processor
>    Affects Versions: 0.2.0
>            Reporter: Raghotham Murthy
>            Assignee: Raghotham Murthy
>            Priority: Minor
>             Fix For: 0.2.0
>
>         Attachments: hive-132.1.patch, hive-132.2.patch
>
>
> Right now there is a different code path in the Driver for show tables/describe etc.
By adding the FetchTask the code paths will be merged. In addition, the results of these statements
will be readable via JDBC.
> Going forward, we should provide SQL access to our metastore similar to access provided
by Oracle or mysql to their catalog tables. In this jira, I will just add schema information
to show tables and describe queries.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message