[
https://issues.apache.org/jira/browse/CASSANDRA-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147777#comment-15147777
]
Paulo Motta commented on CASSANDRA-10625:
-----------------------------------------
bq. How about a single warning, the first time it happens?
Sounds good! Will mark as ready to commit when CI is happy:
||3.0||trunk||
|[branch|https://github.com/apache/cassandra/compare/cassandra-3.0...pauloricardomg:3.0-10625]|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-10625]|
|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-3.0-10625-testall/lastCompletedBuild/testReport/]|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-10625-testall/lastCompletedBuild/testReport/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-3.0-10625-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-10625-dtest/lastCompletedBuild/testReport/]|
committer: patch merges cleanly upwards.
> Problem of year 10000: Dates too far in the future can be saved but not read
> back using cqlsh
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10625
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10625
> Project: Cassandra
> Issue Type: Bug
> Reporter: Piotr Kołaczkowski
> Assignee: Adam Holmberg
> Priority: Minor
> Fix For: 3.0.x, 3.x
>
>
> {noformat}
> cqlsh> insert into test.timestamp_test (pkey, ts) VALUES (1, '9999-12-31
> 23:59:59+0000');
> cqlsh> select * from test.timestamp_test ;
> pkey | ts
> ------+--------------------------
> 1 | 9999-12-31 23:59:59+0000
> (1 rows)
> cqlsh> insert into test.timestamp_test (pkey, ts) VALUES (1, '10000-01-01
> 00:00:01+0000');
> cqlsh> select * from test.timestamp_test ;
> Traceback (most recent call last):
> File "bin/../resources/cassandra/bin/cqlsh", line 1112, in
> perform_simple_statement
> rows = self.session.execute(statement, trace=self.tracing_enabled)
> File
> "/home/pkolaczk/Projekty/DataStax/bdp/resources/cassandra/bin/../zipfiles/cassandra-driver-internal-only-2.7.2.zip/cassandra-driver-2.7.2/cassandra/cluster.py",
> line 1602, in execute
> result = future.result()
> File
> "/home/pkolaczk/Projekty/DataStax/bdp/resources/cassandra/bin/../zipfiles/cassandra-driver-internal-only-2.7.2.zip/cassandra-driver-2.7.2/cassandra/cluster.py",
> line 3347, in result
> raise self._final_exception
> OverflowError: date value out of range
> {noformat}
> The connection is broken afterwards:
> {noformat}
> cqlsh> insert into test.timestamp_test (pkey, ts) VALUES (1, '10000-01-01
> 00:00:01+0000');
> NoHostAvailable: ('Unable to complete the operation against any hosts',
> {<Host: 127.0.0.1 Analytics>: ConnectionShutdown('Connection to 127.0.0.1 is
> defunct',)})
> {noformat}
> Expected behaviors (one of):
> - don't allow to insert dates larger than 9999-12-31 and document the
> limitation
> - handle all dates up to Java Date(MAX_LONG) for writing and reading
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
