I am trying to use MoreLikeThis (both the component and handler,
trying combinations) and I would like to give it an input document
reference which has a "source" field to analyze and then get back
other documents which have a given field that is used by MLT.
My dataset is composed of documents li
I am trying to run a very simple query via the Admin interface and
receive the exception below.
The query is:
description_t:guard AND title_t:help
I am using dynamic fields (hence the underscored suffix).
Any ideas?
Thanks in advance
/cody
Nov 19, 2007 3:01:31 PM org.apache.solr.core.SolrE
For the storyText "field" element, is that wrapping only in this email
or is the source document wrapping like that as well?
/cody
On 4/26/07, Mike <[EMAIL PROTECTED]> wrote:
Greetings
I've gotten SOLR installed and the admin screens working. At this
point I'm just trying to get my add record
What about:
(type:changelog) AND (filename:angel)
Or if you do the 3 different type of filename queries, use parenthesis
to properly break them up, e..g
type:changelog AND (filename:... OR filename:... OR filename:...)
I dont know enough about how Lucene's precedence rules, but you might
have
PERFECT.
Thanks guys/gals.
On 4/19/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 4/19/07, Cody Caughlan <[EMAIL PROTECTED]> wrote:
> How does that work?
From the user perspective, you continue to "see" the previous version
of the index that was last committed un
Ok, cool. At the worse case, are you just not going to get any hits,
even though you "know" the data is in there, but it just hasnt been
indexed yet?
How does that work?
/cody
On 4/19/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 4/19/07, Cody Caughlan <[EMAIL PROTECTED
This is more of a Lucene question than a Solr one, but... is it
possible to query a Solr(Lucene) index while it is in the middle of
performing a commit/optimize?
Some of the Lucene documentation *implies*, but on a logical level it
seems kind of crazy. But at the same time, for applications where
-----+
On Apr 19, 2007, at 10:04 AM, Cody Caughlan wrote:
> Why not just store an additional "object_type" field which
> differentiates between the actual type of data you are looking for?
>
> So if you're looking for some shoes:
>
> (size:8 AND color:
Why not just store an additional "object_type" field which
differentiates between the actual type of data you are looking for?
So if you're looking for some shoes:
(size:8 AND color:'blue') AND object_type:'shoe'
Or if you're searching on brands
(genre:'skater' AND brand_desc:'skater boy') AND
First off, I am aware that the bulk of this question has to do with
Jetty, but please have kindness...
My end goal is to have a handful of Solr instances running under Jetty
all accessible at
/app1
/app2
...etc...
I have taken the .war file in the Solr dist/ directory, unpacked it
and added in
10 matches
Mail list logo
