[
https://issues.apache.org/jira/browse/CASSANDRA-10252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064010#comment-15064010
]
Taiyuan Zhang commented on CASSANDRA-10252:
-------------------------------------------
I'm half way through this. A couple of thoughts:
1. The current implementation is to use regular expression to match the time
string against ALL possible CQL built-in datetime formats. I think this is very
valuable and should be kept
2. Therefore, my idea of implementing this is, first try to parse using the
current regular expression approach; if fail, then try to parse using
user-specified format, coming either from explicit command or cqlshrc
Another thing I want to be clear about is: in this issue it says fix version:
2.1.x. Does this mean I should do the modification on just the trunk branch, or
just the 2.1.x branch, or all branches?
> COPY FROM should respect time_format from cqlshrc
> -------------------------------------------------
>
> Key: CASSANDRA-10252
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10252
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Carl Yeksigian
> Priority: Minor
> Labels: cqlsh, lhf
> Fix For: 2.1.x
>
>
> Currently, {{COPY FROM}} doesn't respect the {{time_format}} property in
> cqlshrc, we only use that for {{COPY TO}}. We should use the same property
> for both to prevent issues like CASSANDRA-8970.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
