Hi,
Thank you for your reply
In other word, can I set 2 unique key field?
Thank you,
Vinci
hossman wrote:
>
>
> : I want to set 2 field that are unique for different kind of searching.
> Does
> : it possible?
>
> not unless you enforce it yourself -- there isn't anything built in to
> Solr
: I am computing a sorted rank list and returning a slice (for pagination) but
: have to recompute the result for each request, although the actual q
: parameter and fq would be cached but not the sorted list which I could cache
: to reuse on subsequent requests.
:
: I might have a look at the cac
: I want to set 2 field that are unique for different kind of searching. Does
: it possible?
not unless you enforce it yourself -- there isn't anything built in to
Solr to do this with the exception of the uniqueKey field.
There is an UpdateRequestProcessorFactory hook that you can implement to
: Actually I want to use anything that is not alphabet or digit to be the
: separator - anything between them will be a word (so that I can use the URL
: fragment to see what is indexed about this site)...any suggestion?
In addition to Mike's suggestion of trying out the WordDelimiterFilter,
tak
Concretely, it would be good to know how your Portuguese Stemmer is
different/better than Porter's.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Monday, March 31, 2008
On Apr 1, 2008, at 1:35 PM, Vinci wrote:
Thank you for your reply, It look like I will have some benefit but
I will
also lose the highlighter/summary functionary, it that right?
Ya can't highlight what you don't have. So that's true.
I think eventually it would be handy for Solr to allow t
Hi,
Thank you for your reply, It look like I will have some benefit but I will
also lose the highlighter/summary functionary, it that right?
Thank you,
Vinci
Erik Hatcher wrote:
>
>
> On Mar 31, 2008, at 11:56 PM, Vinci wrote:
>> I would like to ask, if I set a field to be indexed but not s
I just chatted with Matt about this. It took me a few seconds
(thinking this might be a browser caching issue without looking at
the actual query), but the issue is that dismax does not support the
*:* syntax. Removing the q parameter altogether does the trick, with
it falling back to the
That was the answer I was looking for, I will try that one out
Thanks Daniel
-Original Message-
From: Daniel Papasian [mailto:[EMAIL PROTECTED]
Sent: 01 April 2008 16:03
To: solr-user@lucene.apache.org
Subject: Re: matching exact/whole phrase
Sandeep Shetty wrote:
> Hi people,
>
> I am l
Sandeep Shetty wrote:
Hi people,
I am looking to provide exact phrase match, along with the full text
search with solr. I want to achieve the same effect in solr rather
than use a separate SQL query. I want to do the following as an
example
The indexed field has the text "car repair" (without
Hi people,
I am looking to provide exact phrase match, along with the full text search
with solr. I want to achieve the same effect in solr rather than use a
separate SQL query. I want to do the following as an example
The indexed field has the text "car repair" (without the double quotes) fo
Hi,
I recently started playing with the dismax handler and custom request
handlers. When using the solr.StandardRequestHandler class, I get the
response that I want; lots of facet values. When I switch to the dismax
class, I get none. I've posted my request handler definitions here. Am I
missing s
You *may* want to consider MultiCore:
http://wiki.apache.org/solr/MultiCore
but it may still be more appropriate to install multiple instances.
On Apr 1, 2008, at 2:40 AM, Bhavin Pandya wrote:
I have configured solr instance for one of my application in which
there is one master server and 3
thanks ryan
seems like this would be helpful.
will try it out.
thanks again.
-umar
On Tue, Apr 1, 2008 at 12:13 AM, Chris Hostetter <[EMAIL PROTECTED]>
wrote:
>
> : > 2. Augment the documents with a field value -- this is a bit more
> : > complex and runs the risk of name collisions with field
I'll let the example schema.xml speak for itself:
omitNorms="true"/>
sortMissingLast="true" omitNorms="true"/>
sortMissingLast="true" omitNorms="true"/>
sortMissingLast="true" omitNorms="true"/>
sortMissingLast="true" omitNorms="true"/>
On Apr
On Mar 31, 2008, at 11:56 PM, Vinci wrote:
I would like to ask, if I set a field to be indexed but not stored,
I can
retrieved the document but cannot retrieve this field?
That's correct. By definition :)
If I have large field that I want to index but I am not suppose to
show them
to use
That did the trick. I actually figured it out on my own 10 minutes after
I posted to the mailinglist. Typical ;-)
Thanks for the help anyway everybody!
//Daniel
Uwe Klosa wrote:
You should set uriEncoding="UTF-8" in your application server. For tomcat
you can do that in the server.xml. For Gla
17 matches
Mail list logo