[
https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-9526:
------------------------------
Attachment: SOLR-9526.patch
New patch and updated PR https://github.com/apache/lucene-solr/pull/91
* Fixed bug that did not persist copyFields to schema
See new NOCOMMIT comments. I was using the {{ManagedIndexSchema}} method
{code}
public ManagedIndexSchema addCopyFields(String source, Collection<String>
destinations, int maxChars)
{code}
which does not have a {{persist=true/false}} argument, so calling it leaves the
schema not persisted. Then I could not find a way to explicitly persist it
since method
{code}
boolean persistManagedSchema(boolean createOnly)
{code}
was not public. In this patch I've made it public and done a hacky instanceof
check in {{AddSchemaFieldsUpdateProcessorFactory}}
{code}
if (newSchema instanceof ManagedIndexSchema) {
// NOCOMMIT: Hack to avoid persisting schema once after addFields and then
once after each copyField
((ManagedIndexSchema)newSchema).persistManagedSchema(false);
}
{code}
[~steve_rowe], you wrote the {{addCopyFields()}} method a while ago, is there a
cleaner way to make sure schema is persisted after adding a copyField?
> data_driven configs defaults to "strings" for unmapped fields, makes most
> fields containing "textual content" unsearchable, breaks tutorial examples
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-9526
> URL: https://issues.apache.org/jira/browse/SOLR-9526
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Jan Høydahl
> Attachments: SOLR-9526.patch, SOLR-9526.patch, SOLR-9526.patch,
> SOLR-9526.patch
>
>
> James Pritchett pointed out on the solr-user list that this sample query from
> the quick start tutorial matched no docs (even though the tutorial text says
> "The above request returns only one document")...
> http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=name:foundation
> The root problem seems to be that the add-unknown-fields-to-the-schema chain
> in data_driven_schema_configs is configured with...
> {code}
> <str name="defaultFieldType">strings</str>
> {code}
> ...and the "strings" type uses StrField and is not tokenized.
> ----
> Original thread:
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201609.mbox/%3ccac-n2zrpsspfnk43agecspchc5b-0ff25xlfnzogyuvyg2d...@mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
