On 11-Sep-07, at 8:52 AM, Jack L wrote:
I was going through some old emails on this topic. Rafael Rossini
figured
out how to run multiple indices on single instance of jetty but it
has to
be jetty plus. I guess jetty doesn't allow this? I suppose I can add
additional jars and make it work but I haven't tried that. It'll
always be much safer/simpler/less playing around if a feature is
available out of box.
The example that comes with Solr is meant to be a starting point for
users. It is a relatively functional and well-commented example, and
its config files are pretty much the canonical documentation for solr
config, and for many people they can modifying it for their own
production use....
but it is still just an example application.
By the time people want to do expert-level activities with Solr
(multi-index falls into that category), they should be able to
configure their own servlet container, whether it be jetty plus,
tomcat, resin, etc.
1. it's easier to maintain separate indices. I can just wipe out all
the files and re-post an individual index. Much less posting work to
do as opposed to re-posting all docs. Or I can move one index to
another partition, or even to another server to run separately in
order to scale up. It'll be a problem (although solvable by deleting
and re-posting) with a mixed index.
2. my understanding is that mixed index means larger index files and
slower performance
Both of these are true, but do not typically have to be decided at
minute zero when developing a project with solr. I recent split our
main index into two separate solr installations in a single jettyplus
container and it was less than a day's work (most of it was tweaking
interface code on our side, not the solr config itsefl).
JettyPlus's download links seem to be broken so I wasn't able to check
its download size. If not too big, maybe JettyPlus is an option?
If not, there should be a way to have this feature implemented on solr
side? Maybe by prefixing the REST URLs with index names...
There just might be something like that in 1.3...
-Mike
