You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2016/12/20 22:52:58 UTC

[jira] [Created] (SOLR-9883) example solr config files can lead to invalid tlog replays when using add-unknown-fields-to-schema updat chain

Erick Erickson created SOLR-9883:
------------------------------------

             Summary: example solr config files can lead to invalid tlog replays when using add-unknown-fields-to-schema updat chain
                 Key: SOLR-9883
                 URL: https://issues.apache.org/jira/browse/SOLR-9883
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
    Affects Versions: 6.3, trunk
            Reporter: Erick Erickson


The current basic_configs and data_driven_schema_configs try to create unknown fields. The problem is that the date processing "ParseDateFieldUpdateProcessorFactory" is not invoked if the doc is replayed from the tlog. Whether there are other places this is a problem I don't know, this is a concrete example that fails in the field.

So say I have a pattern for dates that omits the trialing 'Z', as:
yyyy-MM-dd'T'HH:mm:ss.SSS

This work fine when the doc is initially indexed. Now say the doc must be replayed from the tlog. The doc errors out with "unknown date format" since (apparently) this doesn't go through the same update chain, perhaps due to the sample configs defining ParseDateFieldUpdateProcessorFactory after  DistributedUpdateProcessorFactory?





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org