[
https://issues.apache.org/jira/browse/IGNITE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038621#comment-16038621
]
ASF GitHub Bot commented on IGNITE-5420:
----------------------------------------
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2093
IGNITE-5420
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5420
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2093.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 #2093
----
commit 30676c67c61caebcb5be9d885a4c00b3a585bea9
Author: devozerov <[email protected]>
Date: 2017-06-06T10:59:29Z
Done.
commit 90165393b6415792ed9d6fc45b8a5408afae04c6
Author: devozerov <[email protected]>
Date: 2017-06-06T11:02:47Z
WIP
----
> Table key type name and value type must be unique
> -------------------------------------------------
>
> Key: IGNITE-5420
> URL: https://issues.apache.org/jira/browse/IGNITE-5420
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> We need to make sure that key and value type names assigned to query entity
> are globally unique between all tables in the cluster. Otherwise, we may have
> conflicts between tables in different schemas with equal names (not the case
> for 2.1), or within the same table, when we do CREATE -> DROP -> CREATE and
> certain column type is changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
