You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Blackfield (JIRA)" <ji...@apache.org> on 2017/11/28 17:26:00 UTC

[jira] [Created] (IGNITE-7051) SQL Rename table support

Blackfield created IGNITE-7051:
----------------------------------

             Summary: SQL Rename table support
                 Key: IGNITE-7051
                 URL: https://issues.apache.org/jira/browse/IGNITE-7051
             Project: Ignite
          Issue Type: Improvement
          Components: sql
    Affects Versions: 2.3
            Reporter: Blackfield


Use case was discussed at length here: 
http://apache-ignite-users.70518.x6.nabble.com/Continuous-update-Data-Grid-Cache-td2075.html#a17641

Currently, we have to load data to second table, the client then has to 
change their query to query this 
new table. Drop the old table. 

The latest suggestion in the above thread to "load new data set in the same 
cache and remove old entries once preloading is finished" is not feasible 
since for large table and table scan query (thus requires whole dataset to 
be loaded), it will take a while to load everything - thus increasing the 
downtime. 

Table rename support will reduce the downtime greatly. 

Ref: Postgresql and H2 syntax
ALTER TABLE TmpTable RENAME TO Table1; 


Then, one would wrap it within transaction (It appears that this is slated 
for 2.4/2.5?) to drop old table, rename temp table to original table. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)