On Apr 26, 2006, at 9:41 AM, Grant Ingersoll wrote:
Erik Hatcher <[EMAIL PROTECTED]> wrote:
I've been mulling over the idea of having a single Solr instance
morph into system that can handle multiple client-defined schemas
(why not? Lucene itself can handle it) rather than a static XML file
and allow the schemas themselves to be retrievable (yes, I know it
already is). I'm still talking about a single Lucene index, but with
each Document given a "soup" name field and filters automatically
available to single out a specific soup.
I agree.
I also don't think it is going to work well to have one webapp per
index/schema for those of us who want multiple indexes. I think
SOLR needs to be able to support multiple Lucene indexes per WAR
deployment as well (although your soup idea would work well too)
and then allow the requests to specify which index to use, maybe
with some defaults. With this idea, you could even imagine an
application could upload a schema to SOLR and have it create the
index, etc. upon which you could then add documents, etc. No need
to do anything command line at all.
Sorry for my delay on this thread, e-mail is becoming more and more
difficult to manage lately.
Yes, my definitely aiming for a dynamic schema scenario, allowing the
client to specify it entirely (at least within the confines of a
named "soup", where that name would be a field automatically added to
every document being added to that soup). And the schema would be
retrievable upon demand by the client as well.
At least this seems like an interesting avenue to explore!
Erik
