[
https://issues.apache.org/jira/browse/CASSANDRA-17467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511431#comment-17511431
]
Anand B commented on CASSANDRA-17467:
-------------------------------------
Thanks [~brandon.williams] and [~brandon.williams] for quick resolution on this
issue.
How can this fix be up-taken and applied to environment so that it can be
verified if this resolve the raised issue and allow to upgrade from 3.x to
4.x.
do one need to wait till 4.0.4 is out or build can be provided along with this
fix for user's consumption so that upgrade can resume ?
> Timestamp issue with Cassandra 4.0.3 with Timezone value
> --------------------------------------------------------
>
> Key: CASSANDRA-17467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17467
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
> Reporter: Anand B
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.1, 4.0.4
>
>
> 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}
>
> if we change timestamp value From {'2022-03-20 12:48:{color:#de350b}56
> +0530{color}'} To {'2022-03-20 12:48:{color:#ffab00}56+0530{color}’} then
> 4.0.3 accept this value otherwise not. but 3.11 was accepting both the values.
>
> 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.3 which can be used to
> fix this issue asap.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
