[
https://issues.apache.org/jira/browse/SOLR-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke updated SOLR-11855:
---------------------------------------
Attachment: SOLR-11855.patch
> known field's empty value can vanish via add-unknown-fields-to-the-schema
> updateRequestProcessorChain
> -----------------------------------------------------------------------------------------------------
>
> Key: SOLR-11855
> URL: https://issues.apache.org/jira/browse/SOLR-11855
> Project: Solr
> Issue Type: Bug
> Environment: *known field's empty value can vanish via
> add-unknown-fields-to-the-schema updateRequestProcessorChain*
> This appears to be due to the "remove-blank" processor in the
> "add-unknown-fields-to-the-schema" process chain i.e. remove-blank applies to
> known as well as unknown fields (and when field guessing is disabled then
> remove-blank logic also stops).
> Technically there's nothing broken here but I'm wondering if remove-blank
> might be removed (no pun intended) from the _default configuration or if the
> {code}
> WARNING: Using _default configset. Data driven schema functionality is
> enabled by default, which is NOT RECOMMENDED for production use.
> To turn it off:
> curl http://localhost:8983/solr/collectionA/config -d '{"set-user-property":
> {"update.autoCreateFields":"false"}}'
> {code}
> wording might be revised somehow to better account for the remove-blank
> functionality?
> Reporter: Christine Poerschke
> Priority: Trivial
> Attachments: SOLR-11855.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
