ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN
Date Wed, 20 Dec 2017 11:59:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298349#comment-16298349
] 

ASF GitHub Bot commented on IGNITE-5949:
----------------------------------------

GitHub user skalashnikov opened a pull request:

    https://github.com/apache/ignite/pull/3258

    IGNITE-5949: Added limited support for DDL ALTER TABLE DROP COLUMN

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5949

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3258.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3258
    
----
commit 0b438d9dc1887f2d6ed34aca6fef044edfea2c59
Author: skalashnikov <skalashnikov@...>
Date:   2017-12-20T11:53:44Z

    IGNITE-5949: Added limited support for DDL ALTER TABLE DROP COLUMN

----


> DDL: Support ALTER TABLE DROP COLUMN
> ------------------------------------
>
>                 Key: IGNITE-5949
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5949
>             Project: Ignite
>          Issue Type: New Feature
>          Components: sql
>            Reporter: Andrew Mashenkov
>            Assignee: Sergey Kalashnikov
>              Labels: important
>             Fix For: 2.4
>
>
> Ignite should support {{DROP COLUMN}} operation for {{ALTER TABLE}} command.
> Design considerations:
> 1) Drop should only be possible on binary types without schema (see IGNITE-6611). Probably
we will need a new option for {{CREATE TABLE}} command
> 2) Drop should not block other operations for a long time. We should synchronously block
the table, change meta, then release the lock and let operations continue.
> 3) Actual data remove should be performed asynchronously in the same way we create index.
During this time we should not allow any other modifications to the table
> 4) Be careful with node stop - we do not want to wait for years for this command to complete.



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

Mime
View raw message