Nice one worked for me.

On Thu, Aug 2, 2012 at 4:03 PM, Anson Abraham <anson.abra...@gmail.com>wrote:

> pretty much what you did.  I didn't realize that it was in the docs
> already:
>
>
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-DescribeTable%2FColumn
>
> Not sure, but I think this function is supported in 0.6  but I could be
> wrong.
>
>
> On Thu, Aug 2, 2012 at 3:59 PM, Techy Teck <comptechge...@gmail.com>wrote:
>
>> And I got this error too-
>>
>> FAILED: Parse Error: line 1:19 mismatched input 'table1' expecting EOF
>>
>>
>>
>>
>> On Thu, Aug 2, 2012 at 12:44 PM, Techy Teck <comptechge...@gmail.com>wrote:
>>
>>> What format you used? I tried like this and it doesn't works for me-
>>>
>>> *describe formatted table1*
>>>
>>> I am running Hive 0.6. Anything else I need to do before running this
>>> query?
>>>
>>>
>>>
>>>
>>> On Thu, Aug 2, 2012 at 12:13 PM, Igor Tatarinov <i...@decide.com> wrote:
>>>
>>>> Try
>>>> describe formatted <table>
>>>>
>>>> igor
>>>> decide.com
>>>>
>>>> On Thu, Aug 2, 2012 at 12:04 PM, Anson Abraham <anson.abra...@gmail.com
>>>> > wrote:
>>>>
>>>>> is there a way to derive information (schema) off a hive table?
>>>>>
>>>>> doing a describe only shows the clolumn w/ types.
>>>>>
>>>>> But i want to know if a table is like this:
>>>>>
>>>>>  ROW FORMAT   DELIMITED
>>>>>
>>>>>     FIELDS TERMINATED BY '\t'
>>>>>
>>>>>     COLLECTION ITEMS TERMINATED BY '\002'
>>>>>
>>>>>     MAP KEYS TERMINATED BY '\003'
>>>>>
>>>>>   STORED AS INPUTFORMAT
>>>>> 'com.hadoop.mapred.DeprecatedLzoTextInputFormat' OUTPUTFORMAT
>>>>> 'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat';
>>>>>
>>>>>
>>>>>
>>>>> Or like this:
>>>>>
>>>>> ROW FORMAT   DELIMITED
>>>>>
>>>>>     FIELDS TERMINATED BY '\t'
>>>>>
>>>>>   STORED AS INPUTFORMAT 'org.apache.hadoop.mapred.TextInputFormat'
>>>>> OUTPUTFORMAT 'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat';
>>>>>
>>>>>
>>>>> where can i find that info?
>>>>>
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>>
>>>>
>>>
>>
>


-- 
Thanks,
sandeep

Reply via email to