hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Chakka (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-590) Pass type information in genFileSinkPlan
Date Thu, 02 Jul 2009 17:35:47 GMT

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

Prasad Chakka commented on HIVE-590:
------------------------------------

I don't think the new Schema object should be in metastore as it is not going to be used by
it. There is no corresponding object in metadb. It will be used only by HiveServer so it should
be in the thrift interface of HiveServer. Namit and I had a chat about it and he agreed to
move it there.


> Pass type information in genFileSinkPlan
> ----------------------------------------
>
>                 Key: HIVE-590
>                 URL: https://issues.apache.org/jira/browse/HIVE-590
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Raghotham Murthy
>            Assignee: Namit Jain
>             Fix For: 0.4.0
>
>         Attachments: hive.590.1.patch, hive.590.2.patch
>
>
> Right now only column names are being passed between semanticanalyzer and fetchtask.
Once type information is passed, we can use LazySerDe to serialize the data (into json) in
Driver.getResults().
> Driver.getSchema() should then return a new thrift type ResultSchema instead of String:
> {code}
> struct ResultSchema {
>   // column names, types, comments
>  1: list<hive_metastore.FieldSchema> fieldSchemas,
>  // delimiters etc
>  2: map<string, string> properties
> }
> {code}
> Once this is done, the jdbc client can instantiate a simplified serde from the ResultSchema
and parse the query results.

-- 
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