[
https://issues.apache.org/jira/browse/SOLR-9294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371352#comment-15371352
]
Hoss Man commented on SOLR-9294:
--------------------------------
For updates it's already possible to configure your update processor chain to
accept a wide variety of date formats...
https://lucene.apache.org/solr/6_1_0/solr-core/org/apache/solr/update/processor/ParseDateFieldUpdateProcessorFactory.html
...as a general purpose feature of date parsing/formatting in all aspects of
request handling (ie: query parsing, DateRangeField, xml/json response
writting, etc...) the scope of the problem gets much bigger.
I personally think it adds a lot of complexity (both internally and for
clients) and would prefer to stick to one canonical date representation.
> DateMathParser Milliseconds separator
> -------------------------------------
>
> Key: SOLR-9294
> URL: https://issues.apache.org/jira/browse/SOLR-9294
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers
> Affects Versions: 6.1
> Reporter: Curtis Fehr
> Priority: Minor
>
> DateMathParser is no longer accepting the format xxxx-xx-xxTxx:xx:xx:xxxZ
> whereas it did in the past (5.3 works). Changing the milliseconds separator
> to "." fixes the issue, but this is a time consuming change for organizations
> that use many data consumers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
