On 8/1/07, Teruhiko Kurosaka <[EMAIL PROTECTED]> wrote:
> I'm using Solr 1.1.
> I ran:
> post.sh vidcard.xml
> (with URL modified in post.sh) then got an error:
> Posting file vidcard.xml to http://localhost:28080/solr/update
> ERROR: multiple values encountered for non
> multiValued field text: f
I'm using Solr 1.1.
I ran:
post.sh vidcard.xml
(with URL modified in post.sh) then got an error:
Posting file vidcard.xml to http://localhost:28080/solr/update
ERROR: multiple values encountered for non
multiValued field text: f\
irst='ASUS Extreme N7800GTX/2DHTV (256 MB)' second='ASUS Computer
In
On 8/1/07, Daniel Alheiros <[EMAIL PROTECTED]> wrote:
> I'm using the PorterStemmerFilterFactory when indexing but not when
> querying.
That's problematic though. During index time, if "city" is stemmed to
"citi", then a search of "city" will find nothing unless it's stemmed
too.
One should alwa
On Wednesday 01 August 2007 09:47, Chris Hostetter wrote:
> for the record, using the Lucene boolean options "+" and "-" do work in
> the "q" expression for the dismax handler ... for that matter, the
> boolean keywords AND, OR, and NOT work as well
The only case that doesn't seem to work (and th
You get that behavior by avoiding any extra syntax. Use this query:
a:valueAlpha b:valueBeta c:valueGamma
If one of the terms is very common and one is very rare, it might
not sort on pure existance. This is a tf.idf engine.
wunder
On 8/1/07 11:00 AM, "Lance Lance" <[EMAIL PROTECTED]> wrote:
On this subject:
I thought that this query would find at least one of the given values:
+(a:valueAlpha a:valueBeta a:valueGamma)
It would sort returns by 'have all 3', 'have 2', and 'have 1'. In fact, it
only finds records with all three. That is, it is exactly the same as:
+a:va
This caused me a certain amount of trouble, because the parser
errors with ill-formed queries. Try these:
foo -
TO HAVE AND HAVE NOT
wunder
On 8/1/07 12:47 AM, "Chris Hostetter" <[EMAIL PROTECTED]> wrote:
>
> : > StandardRequestHandler), but I also want to be able to use Lucene's
> : > b
Hello,
I've been using Solr in an embedded situation, and its been working quite well.
But as I've started scaling up the application, the logging that Solr does to
stderr is getting excessive.
I'd like to disable the INFO messages, and leave the WARNINGs. According to the
Java API I should
Hi,
In my opinion the results from carrot2 clustering could be used in the same way
that facet results are used.
That's the way I'm planning to use them.
The user of the search application can narrow the search by selecting one of
the facets presented in the search result presentation. These f
Hi
I've narrowed down to realize that my problem here is related to the way I
store/index my fields in a multi-language index... I'm going to explain how
I'm doing it and I hope you can come out with some nice way to solve my
problem:
My schema.xml contains the following definitions:
>
> Has anyone looked into using carrot2 clustering with solr?
>
> I know this is integrated with nutch:
>
> http://lucene.apache.org/nutch/apidocs/org/apache/nutch/clustering/carrot2/Clusterer.html
>
> It looks like carrot has support to read results from a solr index:
>
> http://demo.carrot2.org/
Hi Mike.
Thanks for your reply, but seems that I haven't expressed myself clearly.
Here I go:
I want that when I search for "butter" all words containing "butter" (like
"buttered", "butters" ...) are highlighted.
I'm using the PorterStemmerFilterFactory when indexing but not when
querying.
Rega
: > StandardRequestHandler), but I also want to be able to use Lucene's
: > boolean syntax (AND/OR/NOT). This doesn't seem to be supported by
: > DisMaxRequestHandler. I will need to copy or extend
for the record, using the Lucene boolean options "+" and "-" do work in
the "q" expression for the
: :
: : text^0.5 features^1.0 name^1.2 manu^1.1
: :
: > if the q param is: albino elephant ... what would it mean that text and
: > feature are mandatory? do both words have to appear in text and in
: > feature, or just one in each?
: What I wanted is that 'albino' 'eleph
14 matches
Mail list logo
