[
https://issues.apache.org/jira/browse/SOLR-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2890:
---------------------------
Priority: Major (was: Minor)
Fix Version/s: 4.1
Assignee: Hoss Man
Issue Type: Bug (was: Improvement)
Summary: omitTermFreqAndPositions and omitNorms don't work properly
when used on fieldTypes (was: omitTermFreqAndPositions should be specifiable
on fieldType)
This seems like a really bad bug for two reasons:
1) even if there is a trivial work around, it's the kind of thing that most
users aren't going to be savvy enough to even realize isn't working properly
(ie: it has no obvious "ERROR") ... you really have to go out of your way to
discover that the extra data is in your index even though you asked for it not
to be.
2) it appears to have been broken for years and yet none of the tests anyone
has written in that time have managed to tickle it to make any one notice.
So i spent a bit of time trying to write an exhaustive test of the way all the
diff version specific default props work, to prove that the defaults did what
they should, and that overriding them did what it should -- which lead me to
discover there is a similar problem with omitNorms on fieldTYpes.
I'm updating the summary to note this for future searchers, and i'll attach my
patch with test and fixes for review
> omitTermFreqAndPositions and omitNorms don't work properly when used on
> fieldTypes
> ----------------------------------------------------------------------------------
>
> Key: SOLR-2890
> URL: https://issues.apache.org/jira/browse/SOLR-2890
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 3.4
> Reporter: David Smiley
> Assignee: Hoss Man
> Fix For: 4.1
>
> Attachments: SOLR-2890.patch
>
>
> 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]
