You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2014/03/16 05:56:25 UTC
[jira] [Updated] (SOLR-3953) postingsFormat doesn't work on field,
only on fieldType
[ https://issues.apache.org/jira/browse/SOLR-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-3953:
-------------------------------
Fix Version/s: (was: 4.7)
4.8
> postingsFormat doesn't work on field, only on fieldType
> -------------------------------------------------------
>
> Key: SOLR-3953
> URL: https://issues.apache.org/jira/browse/SOLR-3953
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 4.1
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Fix For: 4.8
>
>
> The following schema config (adding postingsFormat) produces no changes in Solr's behavior. If postingsFormat="BloomFilter" is instead added to a new fieldType and that fieldType is used, then Solr's behavior changes. In my pre-deployment tests, it results in SOLR-3950.
> <field name="did" type="long" indexed="true" stored="true" postingsFormat="BloomFilter"/>
> Having to add a new fieldType for an alternate codec leads to configuration duplication and the potential for confusing problems. I would imagine that most people that are interested in alternate codecs will want to continue using an existing type.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org