lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-920) Cache and reuse IndexSchema
Date Mon, 15 Feb 2010 15:51:27 GMT

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

Noble Paul commented on SOLR-920:
---------------------------------

bq., then all the older versions hang around in the cache forever, right?


nope. The cache key is the FQN of the  file . in replication , the same file is overwritten.
So the cache entry is overwritten

> Cache and reuse IndexSchema
> ---------------------------
>
>                 Key: SOLR-920
>                 URL: https://issues.apache.org/jira/browse/SOLR-920
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>         Attachments: SOLR-920.patch, SOLR-920.patch, SOLR-920.patch
>
>
> if there are 1000's of cores then the cost of loading unloading schema.xml can be prohibitive
> similar to SOLR-919 we can also cache the DOM object of schema.xml if the location on
disk is same.  All the dynamic properties can be replaced lazily when they are read.
> We can go one step ahead in this case. Th IndexSchema object is immutable . So if there
are no core properties then the same IndexSchema object can be used across all the cores

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message