[
https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593305#comment-16593305
]
Vladimir Ozerov commented on IGNITE-9183:
-----------------------------------------
[~ivandasch], [~skosarev], my comments:
1) Changes are applied to both \{{CREATE TABLE}} and \{{ALTER TABLE}}
statements, but only latter is tested. Need to test \{{CREATE TABLE}} command
as well, taking in count the following cases: UUID as a key (unwrapped), UUID
as a value (unwrapped), UUID as a part of a composite key, UUID as a part of
composite value.
2) Does table created from CacheConfiguration with predefined QueryEntity
behave in the same way (i.e. UUID is translated to UUID, not bete[])? We need
to confirm it with tests.
3) Some Ignite users may rely on current behavior in their codd, and this
change may break their applications. We need to allow users to force old
behavior with {{byte[]}}. You can use {{IgniteSystemProperties}} for this.
> Proper handling UUID columns, that are added by DDL.
> ----------------------------------------------------
>
> Key: IGNITE-9183
> URL: https://issues.apache.org/jira/browse/IGNITE-9183
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.5, 2.6
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Daschinskiy
> Priority: Major
> Fix For: 2.7
>
>
> Currently, if we added new UUID columnt thru DDL, it is saved to schema as
> byte[]. So it's impossible to use it with DML without placeholders and put
> values thru cache api without converting UUID to byte[].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
