jira at apache
Jun 25, 2012, 7:10 PM
Post #1 of 1
(42 views)
Permalink
|
|
[jira] [Resolved] (SOLR-2600) ensure example schema.xml has some mention/explanation of per field similarity vs similarityprovider vs (global) similarity
|
|
[ https://issues.apache.org/jira/browse/SOLR-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-2600.
----------------------------
Resolution: Fixed
Committed revision 1353801. - trunk
Committed revision 1353803. - 4x
> ensure example schema.xml has some mention/explanation of per field similarity vs similarityprovider vs (global) similarity
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-2600
> URL: https://issues.apache.org/jira/browse/SOLR-2600
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Hoss Man
> Assignee: Hoss Man
> Priority: Blocker
> Fix For: 4.0
>
>
> when SOLR-2338 was commited, there wasn't yet clear understanding of how much the new feature per field similarity fields (vs custom similarity provider (vs global similarity factory)) should be "advertised" in the example configs, and what type of usage should be encouraged/promoted.
> it's likely that by the time 4.0 is released, new language specific field types will already demonstrate these features, and no additional "artificial" usages of them will be needed, but one way or another we should ensure that they are either demoed or mentioned in comments
--
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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene
|
