You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2018/08/14 20:18:00 UTC
[jira] [Updated] (SOLR-12591) Ensure
ParseDateFieldUpdateProcessorFactory can be used instead of
ExtractionDateUtil
[ https://issues.apache.org/jira/browse/SOLR-12591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-12591:
--------------------------------
Attachment: SOLR-12591.patch
> 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)
>
> Attachments: SOLR-12591.patch
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org