You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2007/10/25 05:32:50 UTC

[jira] Commented: (SOLR-391) Date type parser is overly fussy

    [ https://issues.apache.org/jira/browse/SOLR-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537484 ] 

Yonik Seeley commented on SOLR-391:
-----------------------------------

> However, when it is printed out it does not include the Z at the end.
That would be a bug...

How does one reproduce this?  I checked XML, JSON, Python, and Ruby output writers... they all include the Z for the DateField type.


> Date type parser is overly fussy
> --------------------------------
>
>                 Key: SOLR-391
>                 URL: https://issues.apache.org/jira/browse/SOLR-391
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.2
>            Reporter: Lance Norskog
>            Priority: Trivial
>
> The parser for the Solr 'date' type is overly picky. It requires an entire year-month-day-T-hour-minute-second-Z string.
> However, when it is printed out it does not include the Z at the end. Thus, a naive XSL script that translates the output into an XML that can be re-fed with the Solr input format has to include the trailing Z to get dates to parse.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.