Solr 7.3.0 copyField未按预期工作，Solr 7配置咨询

Hey there! Let's work through your Solr 7.3.0 questions step by step.

You're right—Solr 7 did deprecate the old defaultSearchField setting in the schema, so setting df (default field) directly on the /select handler is the recommended approach now.

Your current config:

<requestHandler name='/select' class='solr.SearchHandler' default='true' df='fullText' q.op='OR' />

is totally valid for setting a default search field and default operator. One quick note though: I don't see a fullText field defined in the schema snippet you shared. If this is the target field for your copyField setup, make sure you've explicitly defined it in your <fields> section first, like this:

<field name="fullText" type="text_general" multiValued="true" indexed="true" stored="false"/>

Without this definition, the df setting will point to a non-existent field, which will cause unexpected search behavior.

CopyField issues almost always boil down to configuration oversights or missing reindexing. Here's a checklist to debug:

• Verify copyField definitions: Double-check that your <copyField> entries are formatted correctly. For example, if you want to copy searchdata into fullText, it should look like:

  <copyField source="searchdata" dest="fullText"/>
  

  Ensure the source field exists in your schema (like your searchdata string field) and the dest field (fullText) is properly defined as mentioned above.
• Check target field properties: The fullText field needs to have indexed="true" if you want to search against it. Setting multiValued="true" is a good practice if you're copying from multiple source fields, as it allows all copied content to be stored as separate values.
• Reindex your data: CopyField only applies during the indexing process. If you added or modified copyField settings after indexing your documents, you'll need to reindex all your data for the changes to take effect. Old documents won't automatically get the copied field values.
• Check Solr logs: Start by looking at Solr's log files (usually in the logs directory of your Solr instance). If there's a problem with your copyField config (like a missing source/dest field), Solr will log an error during startup that points you to the issue.
• Validate field content: Run a test query to see if the fullText field has data. Use something like:

  http://your-solr-url:8983/solr/your-core/select?q=*:*&fl=id,fullText
  

  If the fullText field is empty in the results, the copy isn't working. If it has content but searches aren't returning what you expect, you might need to check the field type's analyzer settings instead.

内容的提问来源于stack exchange，提问作者Brandon Lim