phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samarth Jain <sama...@apache.org>
Subject Re: Can't change TTL using alter table
Date Fri, 04 Mar 2016 18:44:14 GMT
Rafit,

Changing TTL the way you are doing it should work. Do you have any
concurrent requests going on that are issuing some kind of ALTER TABLE
statements? Also, would you mind posting the DDL statement for your table?

- Samarth

On Fri, Mar 4, 2016 at 9:20 AM, Rafit Izhak-Ratzin <rafit@robinsystems.com>
wrote:

> Hi all,
>
> I am looking for a way to change the ttl of a table that already exists.
> I ran the command below and got the warning message shown below:
>
> 0: jdbc:phoenix:localhost> alter table INSTANCE_CPU set ttl=86600;
> 16/02/28 21:39:40 INFO
> client.HConnectionManager$HConnectionImplementation: Closing master
> protocol: MasterService
> 16/02/28 21:39:40 INFO
> client.HConnectionManager$HConnectionImplementation: Closing zookeeper
> sessionid=0x1532b79a8260087
> 16/02/28 21:39:40 WARN query.ConnectionQueryServicesImpl: Attempt to cache
> older version of INSTANCE_CPU: current= 0, new=0
> No rows affected (6.63 seconds)
>
> My environment: Phoenix version 4.5, Hbase version 0.98
>
> Is there anyway to fix this?
> is there any other way to change the TTL of a table?
>
> Thank you in advance,
> --Rafit
>

Mime
View raw message