[
https://issues.apache.org/jira/browse/SOLR-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269603#comment-13269603
]
Jan Høydahl commented on SOLR-3442:
-----------------------------------
I'm not saying anything is "dead". Both the "lucene" queryparser and copyField
has its mission and is supported, and you can mix and match these with DisMax
to fit your needs. But for the example we should select the most useful and
flexible way to show indexing and search, and that is no longer "text"
catch-all and copyField. Aside from it doubling the size of your index, it is
inflexible in that adding or removing a field from search means schema update
and re-indexing. Catch-all fields with copyField can sometimes be used as a
performance optimization, but you do not start in that end.
Maintaining many examples has shown not to be a very good strategy, look at the
multi-core and DIH examples, they lag behind several versions when it comes to
schema version and new solrconfig syntaxes. Instead, a single schema which can
do both the product search and document search use cases well is easy to
achieve. The Velocity GUI can be extended with two tabs if need be, one
"products" tab and one "documents" tab. If we choose the example documents to
index wisely, to be i.e. user guides for the products, we get a nice
connection. You can search for "ipod" and see both products and user guides
matching your search.
> Example schema switch to DisMax instead of CopyField
> ----------------------------------------------------
>
> Key: SOLR-3442
> URL: https://issues.apache.org/jira/browse/SOLR-3442
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Jan Høydahl
> Labels: dismax
>
> Spinoff from SOLR-3439:
> The use of copyField in todays example schema is an anti pattern since we
> indirectly teach people to duplicate most of their content, while most would
> be better off using DisMax, or at least a combination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
