[
https://issues.apache.org/jira/browse/IGNITE-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381921#comment-16381921
]
Sergey Kalashnikov edited comment on IGNITE-7848 at 3/1/18 12:32 PM:
---------------------------------------------------------------------
[~andmed], I have looked into this issue and unfortunately this is kind of
expected behaviour now. Current implementation of DDL ADD and DROP column has a
limitation that it only update meta and does not modify the data itslef. So the
CREATE INDEX and SELECT in your test fail because they see old field data which
are of wrong type. With current implementation you need to clean the old fields
manually first (NULL them with update f.ex).
was (Author: skalashnikov):
[~andmed], I have looked into this issue and unfortunately this is kind of
expected behaviour now. Current implementation of DDL ADD and DROP column has a
limitation does not modify the data. So the CREATE INDEX and SELECT in your
test fail because they see old field data which are of wrong type. With current
implementation you need to clean the old fields manually first (NULL them with
update f.ex).
> On Date type mismatch DDL functionality is broken
> -------------------------------------------------
>
> Key: IGNITE-7848
> URL: https://issues.apache.org/jira/browse/IGNITE-7848
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrew Medvedev
> Priority: Major
> Attachments: DateCannotBeCastTest.java
>
>
> when Date type in value object is originally set as java.util.Date, then
> after ADD COLUMN IF NOT EXISTS and CREATE INDEX on this field, basic SQL
> functionality (SELECT) is broken
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
