You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2011/08/29 20:48:37 UTC
[jira] [Created] (SOLR-2735) cache LuceneFieldType in SchemaField
cache LuceneFieldType in SchemaField
------------------------------------
Key: SOLR-2735
URL: https://issues.apache.org/jira/browse/SOLR-2735
Project: Solr
Issue Type: Improvement
Reporter: Yonik Seeley
Priority: Minor
Lucene added a reusable FieldType (which I'll call LFT since Solr's FieldType has been around since inception). Ironically this has led to Solr going backwards and creating more objects since FieldType.createField() now creates the LFT every time. We should create it once and keep it in SchemaField, or perhaps even have SchemaField implement LFT.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2735) cache LuceneFieldType in SchemaField
Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093141#comment-13093141 ]
Michael McCandless commented on SOLR-2735:
------------------------------------------
Or maybe Solr's FT could extend Lucene's? Maybe some of the properties tracked by Solr's FT could move into Lucene's FT...
> cache LuceneFieldType in SchemaField
> ------------------------------------
>
> Key: SOLR-2735
> URL: https://issues.apache.org/jira/browse/SOLR-2735
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
> Priority: Minor
>
> Lucene added a reusable FieldType (which I'll call LFT since Solr's FieldType has been around since inception). Ironically this has led to Solr going backwards and creating more objects since FieldType.createField() now creates the LFT every time. We should create it once and keep it in SchemaField, or perhaps even have SchemaField implement LFT.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2735) cache LuceneFieldType in SchemaField
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093147#comment-13093147 ]
Yonik Seeley commented on SOLR-2735:
------------------------------------
bq. Or maybe Solr's FT could extend Lucene's?
I dont' think that would buy us anything since Solr's SchemaField can (and normally do) change a whole bunch of properties like indexed, stored, omitNorms, etc. It really needs to be linked to the SchemaField and not the (Solr)FieldType
> cache LuceneFieldType in SchemaField
> ------------------------------------
>
> Key: SOLR-2735
> URL: https://issues.apache.org/jira/browse/SOLR-2735
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
> Priority: Minor
>
> Lucene added a reusable FieldType (which I'll call LFT since Solr's FieldType has been around since inception). Ironically this has led to Solr going backwards and creating more objects since FieldType.createField() now creates the LFT every time. We should create it once and keep it in SchemaField, or perhaps even have SchemaField implement LFT.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org