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

David Smiley commented on SOLR-2890:
------------------------------------

--then change the wiki :-)

But this is still a problem, sure.  It's "minor" because the work-around is 
trivial.

Minor aside:  You should use a regex at the TokenFilter level, not the 
CharFilter.  It's a bit slower at the CharFilter and there might be problems 
with highlighting if you use the regex to change the field length.  CharFilters 
are designed to work in advance of the Tokenizer when you need to modify what 
the Tokenizer sees.  There will never be such a problem with KeywordTokenizer.
                
> omitTermFreqAndPositions should be specifiable on fieldType
> -----------------------------------------------------------
>
>                 Key: SOLR-2890
>                 URL: https://issues.apache.org/jira/browse/SOLR-2890
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 3.4
>            Reporter: David Smiley
>            Priority: Minor
>
> Setting omitTermFreqAndPositions="true" doesn't work when I put it on a 
> fieldType definition for my text field.  It did work when I put it on the 
> field definition.  I think this option and probably all options should be 
> settable at the fieldType level.  I did some investigation and found that the 
> value of this option was being reset on line 54 of TextField.
> FYI I am trying to put this on a field type for use by the SpellCheck 
> component which has no use for term frequencies and positions from the source 
> field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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