[
https://issues.apache.org/jira/browse/SOLR-12591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577145#comment-16577145
]
Bar Rotstein commented on SOLR-12591:
-------------------------------------
After thinking about this for a bit, it seems to me as if having a single point
of date extraction as well as a single string format(Date#toString) for dates
in Solr would be for the better.
Although, I must admit, I am fairly new to this. Perhaps someone with more
experience could provide his opinion.
[~dsmiley], WDYT?
> Ensure ParseDateFieldUpdateProcessorFactory can be used instead of
> ExtractionDateUtil
> -------------------------------------------------------------------------------------
>
> Key: SOLR-12591
> URL: https://issues.apache.org/jira/browse/SOLR-12591
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: master (8.0)
>
>
> ParseDateFieldUpdateProcessorFactory should ideally be able to handle the
> cases that ExtractionDateUtil does in the "extraction" contrib module. Tests
> should be added, ported from patches in SOLR-12561 that enhance
> TestExtractionDateUtil to similarly ensure the URP is tested. I think in
> this issue, I should switch out Joda time for java.time as well (though leave
> the complete removal for SOLR-12586) if it any changes are actually necessary
> – they probably will be.
> Once this issue is complete, it should be appropriate to gut date time
> parsing out of the "extraction" contrib module – a separate issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
