Anand B created CASSANDRA-17467:
-----------------------------------

             Summary: Timestamp issue with Cassandra 4.0.1 with Timezone value
                 Key: CASSANDRA-17467
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17467
             Project: Cassandra
          Issue Type: Bug
            Reporter: Anand B


Hello Team ,

 

Facing one issue related to the timestamp type in cassandra 4.0.3 version . 
This is not repro in 3.11.x and works fine in 3.11.

 

when i have table with timestamp as fields :

 

CREATE TABLE timetest (

    id int PRIMARY KEY,

    enddate timestamp,

    startdate timestamp

)





*Now when try to insert the record like :*





INSERT INTO timetest (id,startdate,enddate) VALUES (1 ,'2022-03-20 12:48:56 
+0530','2022-03-20 12:48:56 +0530')





I am receiving error:

 

"{color:#de350b}InvalidRequest{color}: Error from server: code=2200 [Invalid 
query] message="Unable to parse a date/time from '2022-03-20 12:48:56 +0530'".

 ** 

*This works fine on 3.11 but fails on 4.x.*

 

*same issue if we query the record:*

 

select * from timetest where id = 1 and enddate = '2022-03-20 12:48:56 +0530';





{color:#de350b}InvalidRequest{color}: Error from server: code=2200 [Invalid 
query] message="Unable to parse a date/time from '2022-03-20 12:48:56 +0530'"

 

 

{color:#ffab00}*If we change the timestamp value and remove the extra space 
which is present before the timezone value then it works fine in 4.x*{color}

 

>From {'2022-03-20 12:48:{color:#de350b}56 +0530{color}'} to  ==>  {'2022-03-20 
>12:48:{color:#ffab00}56+0530{color}’}

 

This is causing a challenge for upgrading from 3.11 to 4.x.

 

Seeking help on this issue and any fix / workaround or suitable Cassandra 
version which is higher than 3.11 but lesser then 4.0.1 which can be used to 
fix this issue asap.

 

Regards,

Anand

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to