Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <1030657589.1246485587581.JavaMail.jira@brutus>
Date: Wed, 1 Jul 2009 14:59:47 -0700 (PDT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Updated: (HIVE-590) Pass type information in genFileSinkPlan
In-Reply-To: <941239155.1246303607172.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Namit Jain updated HIVE-590:
----------------------------

    Attachment: hive.590.1.patch

> 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
>         Attachments: hive.590.1.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.