lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3251) dynamically add field to schema
Date Thu, 04 Apr 2013 21:00:16 GMT

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

Steve Rowe commented on SOLR-3251:
----------------------------------

bq. Hmmm, There's already the possibility of sharing schemas, they're cached by path and time
as I remember.

Updating a shared schema will be live for every core that uses it.  Persistence will cause
new cores that are supposed to share to load a new schema object into the cache, but cores
using the no-longer-cached version will continue to use it instead of getting refreshed. 
This will result in partitioning the cores into groups that *really* share schemas.  Maybe
cache keys should use a hash instead of a time stamp?
 
bq. I'm also working on config sets as we speak. Any interactions here that spring to mind?
I suppose I'll have to be looking at invalidating any shared config set if any of the underlying
files change. I admit I haven't looked into the code at all, maybe this'll all be transparent
to the config set caching layer but it'll be a good thing for me to be aware of when I get
back to that JIRA (I've got some work done on it, not testable yet though).

Sorry, I'm not sure about the interactions - what I do know is that since updates are on the
live schema, persistence happens as a side effect of changes - after startup, the persisted
schema is never read again.  Since modifications can only be made after turning on the "managed
schema" facility, external modification can be ignored.  Actually, that argues further for
hashes instead of time stamps for cache keys.

I'm wrapping up testing, and will post a patch soon.  If there are no objections, I'll commit
this in its current state, and we can make further changes, including the caching changes,
on following issues.

                
> dynamically add field to schema
> -------------------------------
>
>                 Key: SOLR-3251
>                 URL: https://issues.apache.org/jira/browse/SOLR-3251
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Yonik Seeley
>            Assignee: Steve Rowe
>         Attachments: SOLR-3251.patch, SOLR-3251.patch
>
>
> One related piece of functionality needed for SOLR-3250 is the ability to dynamically
add a field to the schema.

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message