[ 
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013633#comment-13013633
 ] 

Hoss Man commented on SOLR-2338:
--------------------------------

bq. Do you mean the expert-level SimilarityProvider, 

no i ment the existing global default {{<similarity/>}} mentioned in the 
previous bullet (but i was definitley vague -- sorry).  we probably shouldn't 
go out of our way to advertise the global option anymore, we should encourage 
people to use the fieldType specific similarity instead.

whether we should promote customizing the SimilarityProvider in the example .. 
i dunno, i can see it either way.  but it seems like the order of importance 
for visibility is probably something like:

* customize per fieldType similarity (new hotness)
* customize similarityprovider (not something you are likely to need to do, but 
if you do there's really only one way so maybe we should advertise it's an 
option)
* customize global default similarity (odds are you really don't need this, you 
can probably do it using per fieldType similarity)

> improved per-field similarity integration into schema.xml
> ---------------------------------------------------------
>
>                 Key: SOLR-2338
>                 URL: https://issues.apache.org/jira/browse/SOLR-2338
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>         Attachments: SOLR-2338.patch, SOLR-2338.patch
>
>
> Currently since LUCENE-2236, we can enable Similarity per-field, but in 
> schema.xml there is only a 'global' factory
> for the SimilarityProvider.
> In my opinion this is too low-level because to customize Similarity on a 
> per-field basis, you have to set your own
> CustomSimilarityProvider with <similarity class=.../> and manage the 
> per-field mapping yourself in java code.
> Instead I think it would be better if you just specify the Similarity in the 
> FieldType, like after <analyzer>.
> As far as the example, one idea from LUCENE-1360 was to make a "short_text" 
> or "metadata_text" used by the
> various metadata fields in the example that has better norm quantization for 
> its shortness...

--
This message is automatically generated by JIRA.
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]

Reply via email to