You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Isaac Zhu (Jira)" <ji...@apache.org> on 2021/06/22 03:16:00 UTC
[jira] [Created] (IGNITE-14958) update SQL error "column is not
compatible with index definition" after upgrading to 2.10.0
Isaac Zhu created IGNITE-14958:
----------------------------------
Summary: 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
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)