[
https://issues.apache.org/jira/browse/SOLR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565584#action_12565584
]
Hoss Man commented on SOLR-470:
-------------------------------
I'm notsure i understand your comment ... i don't see any reason why this bug
would have anything to do with DateMathParser -- which only deals with the
"math" portion of an input string (ie: "/HOUR", "+2YEARS", "+6MONTHS+3DAYS/DAY"
etc...) and evaluates them relative some concept of "now" -- the problem seems
to fall squarely on DateField.toObject which assumes it can call call
getThreadLocalDateFormat().parse(...) even though that DateFormat is only
intended for formatting.
Even if we changed DateMathParser as you described i don't see how that would
stop the parser from throwing the "Invalid Date in Date Math String:..."
exception.
> DateField throws error on iso8601 date
> --------------------------------------
>
> Key: SOLR-470
> URL: https://issues.apache.org/jira/browse/SOLR-470
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3
> Reporter: patrick o'leary
> Assignee: Hoss Man
> Fix For: 1.3
>
>
> A correct iso 8601 date 2006-01-01T12:01:00Z throws an error.
> Unparseable date: "2006-01-01T12:01:00Z" at
> org.apache.solr.schema.DateField.toObject(DateField.java:173) at
> org.apache.solr.schema.DateField.toObject(DateField.java:83)
> The ThreadLocalDateFormat requires fractional seconds
> "yyyy-MM-dd'T'HH:mm:ss.SSS"
> to parse with simple date format. Where as the jdoc states their optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
