There should be a full stack trace somewhere either in the client side log
on the job logs.
³serious error² is usually ORC complaining about some sort of data
corruption.
On 9/14/16, 11:16 AM, "naveen mahadevuni" <nmahadev...@gmail.com> wrote:
>Hi Wei,
>I'm using the hive shell.
>
>Thanks,
>Naveen
>
>On Wed, Sep 14, 2016 at 8:01 PM, Wei Zheng <wzh...@hortonworks.com> wrote:
>
>> Hi Naveen,
>>
>> Which client are you using? Beeline?
>>
>> Thanks,
>> Wei
>>
>> On 9/14/16, 18:25, "naveen mahadevuni" <nmahadev...@gmail.com> wrote:
>>
>> Hi,
>>
>> I'm using Hive 1,.2. From a non-ACID hive session, I performed the
>> following operations and Hive reports 'serious problem'.
>>
>> CREATE TABLE test5(
>> i int,
>> j int)
>> CLUSTERED BY (i) INTO 8 BUCKETS
>> STORED AS ORC
>> TBLPROPERTIES ('transactional'='true');
>>
>> insert into test5 values(1,2);
>> insert into test5 values(3,4);
>>
>> select * from test5; -- Fails reporting serious problem.
>>
>> *-->Failed with exception java.io.IOException:java.lang.
>> RuntimeException:
>> serious problem*
>>
>> Hive documents "Reading/writing to an ACID table from a non-ACID
>> session is
>> not allowed.". Can a better message be reported rather than 'serious
>> problem'?
>>
>> Thanks,
>> Naveen
>>
>>
>>
