Re: Can't change TTL using alter table

Also, are you using the open source version or a vendor supplied distro? On Fri, Mar 4, 2016 at 10:44 AM, Samarth Jain wrote: > 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

Re: Can't change TTL using alter table

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

Can't change TTL using alter table

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

Re: Phoenix Query Server Avatica Upsert

Yeah, I don't think the inclusion of Python code should be viewed as a barrier to inclusion (maybe just a hurdle). I've seen other projects (Ambari, iirc) which have tons of Python code and lots of integration. The serialization for PQS can be changed via a single configuration property in