Mike,
I am currently evaluating different search engine technologies (esp., open
source ones), and this is very interesting to me, for the following reasons:
Our data is much like yours in that we have different types of data
(abstracts, fulltext, music, etc...), which eventually fall under diffe
The crux of the issue seems to be supporting multiple indexes within a
single JVM. This has come up before, and personally i'm still in favor of
implimenting this via multiple webapps in the same servlet container,
rather then a single webapp with many seperate configs/schemas/cores that
it choos
Michael,
I'm not sure that objectType should be tied to which index something
is stored in.
If Solr does evolve multiple index support, one usecase would be
partitioning data based on other factors than objectType
(documentType).
It would seem more flexible for clients (the direct updater or quer
On 4/13/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> This has come up before, and personally i'm still in favor of
> implimenting this via multiple webapps in the same servlet container
That would certainly be easier (and you bring up a good point about
probably wanting different solrconfigs f
Hello there. I moved from Lucene to Solr and am thus far impressed with the
speed, even with the added XML transport necessary to send and receive data.
However, one thing I did like about the Lucene implementation was the
ability to specify indices for each invocation.
I agree with Michael
Hi all,
Just checking - it seems that only indexed fields can specified for
sorting purposes in the query string, or at least that's what I'm
seeing for a date field.
Is this correct? Did I miss this info on the wiki someplace?
And if it is the case, then it would be handy for
StandardReque
: Just checking - it seems that only indexed fields can specified for
: sorting purposes in the query string, or at least that's what I'm
: seeing for a date field.
correct -- Solr uses Lucene's built in sorting, and Lucene requires that
the field be indexed and un-tokenized.
: Is this correct? D
I definitely like the idea of support for multiple indexes based on
partitioning data that is NOT tied to a predefined element named
objectType. If we combine this with Chris' mention of completing the
work to support multiple schemas via multiple webapps in the same
servlet container, then I no lo
Hi all,
I've got some fields that will contain embedded XML. Two questions
relating to that:
1. It appears as though I'll need to XML-escape the field data, as
otherwise Solr complains about find a start tag (one of the embedded
tags) before it finds the end tag for a field.
Is this an exp
