[
https://issues.apache.org/jira/browse/IGNITE-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isaac Zhu resolved IGNITE-14958.
--------------------------------
Fix Version/s: 2.10
Resolution: Not A Bug
We found this is because we store "Date" type in a "Timestamp" column.
This would not cause a problem in previous versions.
> update SQL error "column is not compatible with index definition" after
> upgrading to 2.10.0
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-14958
> URL: https://issues.apache.org/jira/browse/IGNITE-14958
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.10
> Reporter: Isaac Zhu
> Priority: Blocker
> Fix For: 2.10
>
>
> We have an table "issues" which has columns:
> ID int, ASSINED_DATE timestamp, CATEGORY varchar
> This table is created and inserted with data on 2.7.6
>
> After upgrading to 2.10.0, when I ran updating SQL:
> update issue set category = 'A' where CATEGORY = 'B';
> It errors:
> {color:#de350b}*Error: Type for a column 'ASSIGNED_DATE' is not compatible
> with index definition. Expected 'Timestamp', actual type 'Date'
> (state=50000,code=1)*{color}
>
> {color:#172b4d}I tried drop the index of ASSIGNED_DATE, the updating SQL then
> works well.{color}
> {color:#172b4d}But, If I recreate the index of the ASSIGNED_DATE, the
> updating SQL not working again.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
