Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 26 Jul 2011 23:31:10 +0000 (UTC)
From: "Carl Steinbach (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <297605789.9812.1311723070755.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HIVE-274) User cannot specify schema of the
 script output, only the column names can be specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Carl Steinbach updated HIVE-274:
--------------------------------

    Fix Version/s: 0.5.0

> User cannot specify schema of the script output, only the column names can be specified
> ---------------------------------------------------------------------------------------
>
>                 Key: HIVE-274
>                 URL: https://issues.apache.org/jira/browse/HIVE-274
>             Project: Hive
>          Issue Type: New Feature
>          Components: Query Processor
>            Reporter: Namit Jain
>             Fix For: 0.5.0
>
>
> Consider the test: mapreduce1.q:
> FROM src
> INSERT OVERWRITE TABLE dest1
> MAP src.key, CAST(src.key / 10 AS INT), CAST(src.key % 10 AS INT), src.value
> USING '/bin/cat' AS (tkey, ten, one, tvalue)
> DISTRIBUTE BY tvalue, tkey
> SORT BY ten, one;
> Although, in the MAP input, the user is casting the inputs as INT (ten, one), the reduce output ('/bin/cat') still treats them as string, and the sorting happens assuming them as strings - even if the
> user wanted to have integer sorting, the output has lexicographic sorting (look at the output mapreduce1.q.out).
> In the AS, the user should be able to specify the schema in the same way as CREATE TABLE.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira