All -
My apologies in advance of a rather long email message, especially for
a first time poster to this list. I'm looking at using SOLR to
replace our custom http / xml infrastructure for Lucene that we built
to tightly integrate with our web apps running in an oracle, non java
environment.
Eval
partitioned into much smaller sets (e.g. 1-10% of the total
document space), creating separate indexes gives us a much higher
boost in performance.
-Mike
-Original Message-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: Wed 4/12/06 11:54 AM
To: solr-user@lucene
omehow,
perhaps using an existing index as a template.
On 4/12/06, Bryzek.Michael <[EMAIL PROTECTED]> wrote:
> We did rough tests and found that creating multiple indexes performed
> better at run time, especially as the logic to determine what results
> should be presented to which c
Yonik already added support for multiple webapp instances (with unique
schemas) to the Near Term task list ... i've also added a
brainstorming page to the wiki with some ideas for implimenting index
partitioning to the "Ideas for the future" section...
http://wiki.apache.org/solr/TaskList
I defined objectTypes as:
* Share almost everything in the global schema file (e.g. caching,
dynamic fields, field types, etc.)
* Each objectType defined its own set of available fields
This allowed me to easily index completely different types of objects w/
NO way to query across the differ
