hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bala Krishna Gangisetty <b...@altiscale.com>
Subject Re: Updating ORC table fails with [Error 10122]: Bucketized tables do not support INSERT INTO:
Date Fri, 29 Jul 2016 19:43:31 GMT
>
> 'ransactional'='true',


This looks suspicious.

On Fri, Jul 29, 2016 at 12:04 PM, Mich Talebzadeh <mich.talebzadeh@gmail.com
> wrote:

>
> Table was created as ORC transactional table
>
> CREATE TABLE `payees`(
>   `transactiondescription` string,
>   `hits` int,
>   `hashtag` string)
> CLUSTERED BY (
>   transactiondescription)
> INTO 256 BUCKETS
> ROW FORMAT SERDE
>   'org.apache.hadoop.hive.ql.io.orc.OrcSerde'
> STORED AS INPUTFORMAT
>   'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat'
> OUTPUTFORMAT
>   'org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat'
> LOCATION
>   'hdfs://rhes564:9000/user/hive/warehouse/accounts.db/payees'
> TBLPROPERTIES (
>   'last_modified_by'='hduser',
>   'last_modified_time'='1469818104',
>   'numFiles'='256',
>   'numRows'='620',
>   'orc.compress'='ZLIB',
>   'ransactional'='true',
>   'rawDataSize'='0',
>   'totalSize'='113650',
>   'transient_lastDdlTime'='1469818104')
>
>
> Updating column hashtag in this table based on column
> transactiondescription
>
> it fails
>
> hive> update payees set hashtag = "HARRODS" here transactiondescription
> like "%HARRODS%";
> FAILED: ParseException line 1:38 missing EOF at 'here' near '"HARRODS"'
> hive> update payees set hashtag = "HARRODS" where transactiondescription
> like "%HARRODS%";
>
> FAILED: SemanticException [Error 10122]: Bucketized tables do not support
> INSERT INTO: Table: accounts.payees
>
>
> What would be the least painful solution without some elaborate means?
>
> Thanks
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>
>
>

Mime
View raw message