[
https://issues.apache.org/jira/browse/CASSANDRA-19566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839670#comment-17839670
]
Stefan Miklosovic commented on CASSANDRA-19566:
-----------------------------------------------
configuration_test.TestConfiguration test_change_durable_writes is
CASSANDRA-19465 which I see returning back recently, nothing to do with this
patch though.
write_failures_test.TestWriteFailures test_mutation_v5 passes locally
[CASSANDRA-19566-trunk|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19566-trunk]
{noformat}
java17_pre-commit_tests
✓ j17_build 4m 43s
✓ j17_cqlsh_dtests_py311 6m 54s
✓ j17_cqlsh_dtests_py311_vnode 7m 36s
✓ j17_cqlsh_dtests_py38 7m 26s
✓ j17_cqlsh_dtests_py38_vnode 7m 30s
✓ j17_cqlshlib_cython_tests 7m 43s
✓ j17_cqlshlib_tests 8m 45s
✓ j17_dtests 36m 55s
✓ j17_unit_tests 13m 17s
✓ j17_utests_latest 13m 54s
✕ j17_dtests_latest 36m 42s
configuration_test.TestConfiguration test_change_durable_writes
✕ j17_dtests_vnode 36m 23s
write_failures_test.TestWriteFailures test_mutation_v5
✕ j17_jvm_dtests 30m 39s
org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
testOptionalMtlsModeDoNotAllowNonSSLConnections TIMEOUTED
org.apache.cassandra.distributed.test.tcm.SplitBrainTest
testSplitBrainStartup TIMEOUTED
✕ j17_jvm_dtests_latest_vnode 28m 39s
junit.framework.TestSuite
org.apache.cassandra.fuzz.harry.integration.model.InJVMTokenAwareExecutorTest
TIMEOUTED
org.apache.cassandra.distributed.test.tcm.SplitBrainTest
testSplitBrainStartup TIMEOUTED
✕ j17_utests_oa 13m 38s
org.apache.cassandra.tcm.DiscoverySimulationTest discoveryTest
{noformat}
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4209/workflows/c5bb9ae4-b124-412e-90ac-8bb2657d1a2c]
> JSON encoded timestamp value does not always match non-JSON encoded value
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-19566
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19566
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
> Reporter: Bowen Song
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Description:
> "SELECT JSON ..." and "toJson(...)" on Cassandra 4.1.4 produces different
> date than "SELECT ..." for some timestamp type values.
>
> Steps to reproduce:
> {code:java}
> $ sudo docker pull cassandra:4.1.4
> $ sudo docker create --name cass cassandra:4.1.4
> $ sudo docker start cass
> $ # wait for the Cassandra instance becomes ready
> $ sudo docker exec -ti cass cqlsh
> Connected to Test Cluster at 127.0.0.1:9042
> [cqlsh 6.1.0 | Cassandra 4.1.4 | CQL spec 3.4.6 | Native protocol v5]
> Use HELP for help.
> cqlsh> create keyspace test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 1};
> cqlsh> use test;
> cqlsh:test> create table tbl (id int, ts timestamp, primary key (id));
> cqlsh:test> insert into tbl (id, ts) values (1, -13767019200000);
> cqlsh:test> select tounixtimestamp(ts), ts, tojson(ts) from tbl where id=1;
> system.tounixtimestamp(ts) | ts |
> system.tojson(ts)
> ----------------------------+---------------------------------+----------------------------
> -13767019200000 | 1533-09-28 12:00:00.000000+0000 | "1533-09-18
> 12:00:00.000Z"
> (1 rows)
> cqlsh:test> select json * from tbl where id=1;
> [json]
> ---------------------------------------------
> {"id": 1, "ts": "1533-09-18 12:00:00.000Z"}
> (1 rows)
> {code}
>
> Expected behaviour:
> The "select ts", "select tojson(ts)" and "select json *" should all produce
> the same date.
>
> Actual behaviour:
> The "select ts" produced the "1533-09-28" date but the "select tojson(ts)"
> and "select json *" produced the "1533-09-18" date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
