[
https://issues.apache.org/jira/browse/SOLR-10948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064019#comment-16064019
]
ASF subversion and git services commented on SOLR-10948:
--------------------------------------------------------
Commit 9f56698d33d1db9fab6a0d6f63b360b334f71583 in lucene-solr's branch
refs/heads/master from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9f56698 ]
SOLR-10948: Fix extraction component to treat DatePointField the same as
TrieDateField
SOLR-10947: Randomize the usage of Points based numerics in contrib test schemas
This commit also adds @SuppressPointFields needed for SOLR-10949
> Extraction contrib doesn't format dates properly when using DatePointField
> --------------------------------------------------------------------------
>
> Key: SOLR-10948
> URL: https://issues.apache.org/jira/browse/SOLR-10948
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - Solr Cell (Tika extraction)
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: master (7.0)
>
>
> SolrContentHandler has a hard coded assumption about TrieDateField that
> causes it to fail if you attempt to use it w/o DatePointField -- because it
> passes the Date as a string in the incorrect format.
> A workaround is to explicitly configure the
> ParseDateFieldUpdateProcessorFactory for any field using the DatePointsField
> type
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
