[
https://issues.apache.org/jira/browse/CASSANDRA-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415404#comment-13415404
]
Jonathan Ellis commented on CASSANDRA-4441:
-------------------------------------------
+1, but I'd rather push this to 1.2 only, since DateType has behaved this way
since 0.8.
> Fix validation of dates
> -----------------------
>
> Key: CASSANDRA-4441
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4441
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.2
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.1.3
>
> Attachments: 4441.txt
>
>
> Our date validation (timestamp type) doesn't validate that the date is
> correct, i.e. it allows dates like 2011-42-42, because DateUtils.parseDate()
> doesn't do the validation (don't ask me how it can generate a timestamp from
> bogus date, apparently it can).
> The easy fix is to use DateUtils.parseDateStrictly(), which does the
> validation. This does require to update commons-lang to >= 2.5 (we have 2.4).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
