You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/28 13:42:00 UTC
[jira] [Commented] (IGNITE-7843) SQL: ALTER TABLE DROP column may
break certain SQL queries
[ https://issues.apache.org/jira/browse/IGNITE-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380321#comment-16380321 ]
ASF GitHub Bot commented on IGNITE-7843:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/3586
IGNITE-7843: refresh index column ids on DROP COLUMN.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7843
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3586.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 #3586
----
commit f96e51fe11c9ca141f1482dbfa7c2256ab32d5e9
Author: skalashnikov <sk...@...>
Date: 2018-02-28T13:40:20Z
IGNITE-7843: refresh index column ids on DROP COLUMN.
----
> SQL: ALTER TABLE DROP column may break certain SQL queries
> ----------------------------------------------------------
>
> Key: IGNITE-7843
> URL: https://issues.apache.org/jira/browse/IGNITE-7843
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.4
> Reporter: Sergey Kalashnikov
> Assignee: Sergey Kalashnikov
> Priority: Blocker
>
> The command DROP table leads to subsequent SQL errors if there is some indexed field next to removed field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)