hossman wrote:
>
>
> I'm not sure i understand what you mwan. Why would protected words (in
> regards to the stemmer) reduce recall ? ... i guess it depends on the
> words you are protecting right ... but why would you wnat to reduce
> recall? isn't the goal usually to increases recall wh
Hi Daniele,
I do not know if the italian anaylzer also has this feature, but the german
analyzer supports a list of words that are not stemmed in al file protwords.txt
Stopwords are propably the wrong direction because it would remove the
configured words from indexing altogether...
@hoss: rec
: because lucene 2.3.0 today released..
It doesn't really work that way.
The Development version of Solr has alreayd been upgradd to Lucene 2.3.0,
but there is other code in Solr ... the Solr code :) ... and it's not
currently in what i would consider in a "releasable" state at the moment.
It
If you would like to work with Lucene 2.3.0, it's been updated in SVN.
I've been using the SVN head version for a while, and it's quite
stable (only thing is conf files and apis change from time to time).
You can get the latest by doing..
svn co http://svn.apache.org/repos/asf/lucene/solr/tr
Hello all,
I'm not sure if this is a Solr question, but any pointers would be
helpful. I am seeing this kind of thing in the stdout logs (I believe
it to be entirely normal):
[10:58:26.507] /select
qt=relatedinstructables&q=music%0awall%0amount%0aguitar%0adiy%0astand%0amusicianhome+NOT+E7Z1HY8HQ
+ 1
Looking forward to get new release version :)
On Jan 28, 2008 6:01 AM, j. L <[EMAIL PROTECTED]> wrote:
> because lucene 2.3.0 today released..
>
>
>
> --
> regards
> j.L
>
--
Best regards,
Traut
URL query:
http://orasupport.ouls.ox.ac.uk:8080/solr/select/?q=bishop&wt=xslt&tr=at
om.xsl
Solr home is located at /home/bugz/solr and tomcat home is at
/home/bugz/fedora/tomcat. The solr home is set in the CATALINA_OPTS
environment var. Note that other search types work fine - removing wt,
or ch
Trying to create my own response writer. I have subclassed TextResponseWriter
and implemented QueryResponseWriter, registered the response writer in solr
config. When jetty starts, I get...
SEVERE: org.apache.solr.core.SolrException: Error instantiating class class
myResponseWriters.DojoRespo
: [10:58:26.507] /select
:
qt=relatedinstructables&q=music%0awall%0amount%0aguitar%0adiy%0astand%0amusicianhome+NOT+E7Z1HY8HQ5ES9J4QIQ&version=2.2&rows=8&wt=json
: 0 341
:
: I don't know how to interpret the last items on the line, though (0
: 341). It appears that Solr uses the Java Logging AP
Thanks Hoss, so then it's actually the same values as returned in the
query response header, e.g. (JSON format):
{"responseHeader":{"status":0,"QTime":209},"response":{"numFound":2574,
... (omitted)
thx,
Rachel
On 1/28/08, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> : [10:58:26.507] /select
>
: Thanks Hoss, so then it's actually the same values as returned in the
: query response header, e.g. (JSON format):
i believe so yes.
-Hoss
I need some clarification on the cache size parameters in the solrconfig.
Suppose I'm using these values:
What does size="5" mean... Is this 5 bytes, kilobytes, megabytes... or
is it the number of documents
that can be cached?
In other words, how do I calculate the memory usage ba
We're now running several solr instances on quad-cores and getting fairly good
RPS even on
the largest index (26MM documents) after implementing faceted queries. Things
are looking good
except for this OutOfMemoryError which occurs every 2 hrs at peak.
Note: I have browsed, searched the forum
On Jan 28, 2008, at 6:05 PM, Alex Benjamen wrote:
I need some clarification on the cache size parameters in the
solrconfig. Suppose I'm using these values:
A lot of this is here: http://wiki.apache.org/solr/SolrCaching
Performing a '' command on the Solr server will force it to open a new
IndexReader, and make your changes visible.
Thanks,
Stu
-Original Message-
From: "Owens, Martin" <[EMAIL PROTECTED]>
Sent: Monday, January 28, 2008 5:38pm
To: solr-user@lucene.apache.org
Subject: Indexing Directly, s
On Jan 28, 2008, at 7:06 PM, Leonardo Santagada wrote:
On 28/01/2008, at 20:44, Alex Benjamen wrote:
I could allocate more physical memory, but I can't seem to increase
the -Xmx option to 3800 I get
an error : "Could not reserve enough space for object heap", even
though I have more than
On 28/01/2008, at 20:44, Alex Benjamen wrote:
Note: I have browsed, searched the forums for this error and
followed the most common advice of
increasing the memory allocation for the JVM:
/usr/bin/java -DSTOP.PORT=8805 -DSTOP.KEY=solrstop -Xmx3584M -
Xms1024M -jar start.jar
[snip]
I cou
>We use 10GB of ram in one of our solr installs. You need to make sure
>your java is 64 bit though. Alex, what does your java -version show?
>Mine shows
>java version "1.6.0_03"
>Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
>Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed m
But on Intel, where I'm having the problem it shows:
java version "1.6.0_10-ea"
Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b10)
Java HotSpot(TM) Server VM (build 11.0-b09, mixed mode)
I can't seem to find the Intel 64 bit JDK binary, can you pls. send
me the link?
I was downloading f
>Install the AMD64 version. (Confusingly, AMD64 is a spec name for
>EM64T, which is now what both AMD and Intel use)
>If that still doesn't work, is it possible that your machine/kernel is
>not set up to support 64 bit?
I was confused by the naming convention. Seems to work fine now, well,
I me
20 matches
Mail list logo
