cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13185) cqlsh COPY doesn't support dates before 1900 or after 9999
Date Tue, 21 Feb 2017 21:24:44 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876752#comment-15876752
] 

Tyler Hobbs commented on CASSANDRA-13185:
-----------------------------------------

bq. Cqlsh COPY is already capable of importing dates as milliseconds from the epoch, this
is the fallback in case the date cannot be parsed.

Okay, awesome.  The C* patch looks perfect to me, then.  For some reason, the 3.11 and trunk
tests failed to run.  I've restarted them, and if they look good, then I think this is ready
to commit.

> cqlsh COPY doesn't support dates before 1900 or after 9999
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-13185
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13185
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Tyler Hobbs
>            Assignee: Stefania
>             Fix For: 3.0.x, 3.11.x
>
>
> Although we fixed this problem for standard queries in CASSANDRA-10625, it still exists
for COPY.  In CASSANDRA-10625, we replaced datetimes outside of the supported time range with
a simple milliseconds-since-epoch long.  We may not want to use the same solution for COPY,
because we wouldn't be able to load the same data back in through COPY.  Having consistency
in the format of values and support for loading exported data seems more important for COPY.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message