instances inside one
Jetty container. I'm using Solr 1.2.0 and Jetty 6.1.3 respectively.
Hope this helps,
--matt
On Sep 11, 2007, at 11: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
respectively.
Hope this helps,
--matt
On Sep 11, 2007, at 11: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
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
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
it on a production server.
That's exactly what I did and it has been working great.
If multiple indices feature is available out of the box, it'll become
another great feature that's easily accessible for entry level users,
like me :)
There just might be something like that in 1.3...
I'm looking
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
webapps within a single container/
process/jvm
In the future, (1.3 or farther down the line), another option will be:
3. multiple indices within a single solr webapp, added/removed on the
fly.
-Mike
indices
: I have multiple applications (blogs/forums/video/etc) - each of these
: is independent (no need to perform queries on multiple indices).
: Would it be best to use multiple instances of SOLR/JVM - one for each
: index or use a solution where only one JVM instance is running (maybe
: Hm, that JNDI again... this makes it sound like SOLR-215 is completely
: superfluous?
No ... i still haven't had a chance to review the patch, but Henri makes
some great argmuments for the WHY of the patch in the issue
description...
Multiple cores:
Deployment issues within some
dear solrs - thanks for all your help.
I have multiple applications (blogs/forums/video/etc) - each of these is
independent (no need to perform queries on multiple indices).
Would it be best to use multiple instances of SOLR/JVM - one for each index
or use a solution where only one JVM
@lucene.apache.org
Sent: Tuesday, June 26, 2007 3:57:12 PM
Subject: multiple indices
dear solrs - thanks for all your help.
I have multiple applications (blogs/forums/video/etc) - each of these is
independent (no need to perform queries on multiple indices).
Would it be best to use multiple instances
On Jan 8, 2007, at 3:13 AM, Chris Hostetter wrote:
: with a single schema -- but dynamicFields are used to store
category
: specific fields, so that if you are doing a category specific
search,
: category specific filters can be offered to you...
:
:
: http://cnet.search.com/search?chkpt=astg.cnet.fd.search.cnetq=canontag=srch
I just so happen to have a bit of insight into how that page works, and
while it's true that it queries multiple indexes with differnet schemas,
it makes no attepts to merge the results -- the product results come
from
On 1/9/07, Mekin Maheshwari [EMAIL PROTECTED] wrote:
Is there any cost to using dynamicFields ?
Very little. A dynamicField is created on demand during indexing or
searching, but the SchemaField created only has 4 pointers in it.
dynamicField is a Solr concept, not a Lucene one... so the
+2 cents:
At 2:43 PM +0530 1/9/07, Mekin Maheshwari wrote:
In general I felt that smaller indexes with different requirements
might be more flexible than 1 large index (Would a 3G index
considered large ?). eg. backing up the index, deploying a fresh
index, etc. But Solr does address most of
: with a single schema -- but dynamicFields are used to store category
: specific fields, so that if you are doing a category specific search,
: category specific filters can be offered to you...
:
: http://shopper.cnet.com/4144-6501_9-0-1.html?query=canon
:
: Could you elaborate a bit more
On Jan 5, 2007, at 1:59 AM, Chris Hostetter wrote:
: The issue is best described with an example:
: search for canon - matches multiple categories, which will have very
: different schemas
: http://cnet.search.com/search?
chkpt=astg.cnet.fd.search.cnetq=canontag=srch
I just so happen to
Thanks Chris.
http://wiki.apache.org/solr/FederatedSearch
Thats useful I might be getting close to that size soon.
The issue is best described with an example:
search for canon - matches multiple categories, which will have very
different schemas
: The issue is best described with an example:
: search for canon - matches multiple categories, which will have very
: different schemas
: http://cnet.search.com/search?chkpt=astg.cnet.fd.search.cnetq=canontag=srch
I just so happen to have a bit of insight into how that page works, and
while
: norms, term vectors, field caches, etc. It almost sounds like one
: would want multiple instances of Solr in the same app container. But
: if that's the case, you aren't saving much over just having multiple
: app servers.
I didn't say anything yesterday because i pretty much agreed with
On 3/21/06, Grant Ingersoll [EMAIL PROTECTED] wrote:
I was wondering if it is possible to have one SOLR instance host multiple
indices? Otherwise, I would need to deploy a separate WAR for every SOLR
instance I want, correct?
It's not currently possible. A fair amount would have to change
21 matches
Mail list logo
