On Sep 13, 2007, at 12:50 PM, Matthew Runo wrote:
Can you not facet on fields which are not indexed? Am I missing
something here?
No. Faceting works off of "terms", which are either the exact field
value for unanalyzed fields, or the tokens that result from the
configured analyzer. Eith
Thanks, I ran into the problem when I issued the commit command to the
SOLR search server.
-Original Message-
From: J.J. Larrea [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 13, 2007 2:29 PM
To: solr-user@lucene.apache.org
Subject: Re: NFS Stale handle in a distributed SOLR deploym
: We are getting very frequent errors of this nature in our jetty-stdout log:
:
: SEVERE: Error during auto-warming of key:
: [EMAIL PROTECTED]:java.lang.NullPointerException
:at org.apache.lucene.search.FieldSortedHitQueue.(
: FieldSortedHitQueue.java:60)
:at org.apache.solr.sear
On 13-Sep-07, at 8:00 AM, Sanjeev Koranga wrote:
Hi,
I am facing a issue with facet fields.
I have one field as category in my schema.xml file and i have
mapped it to facet fields. But the problem is, one of the category
is "Repository" which is displaying fine in category field but in
f
Sometimes one has to make things work in the environment one is handed (e.g.
virtualized servers, ALL storage resources resident on a SAN and accessed via
NFS, read-only mounts on the deployment instances with only the production
indexers having write access). While I agree that fast local inde
I am facing a issue with facet fields.
I have one field as category in my schema.xml file and i have
mapped it to facet fields. But the problem is, one of the category
is "Repository" which is displaying fine in category field but in
facet field it is showing "Repositori". y is getting chan
Are you using Tomcat with Solr? If so you need to add the URIEncoding attribute
to your Connector. See this url -
http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
I hope this helps. If you are using Jetty then . :)
Aaron
-Original Message-
From: Marc Bechler [mailto:[EMAIL
If you are using tomcat, try adding "URIEncoding="UTF-8" to your tomcat
connector.
use the analysis page of the admin interface to check to see what's
happening to your queries, too.
http://localhost:8080/solr/admin/analysis.jsp?highlight=on (your port # may
vary)
Tom
On 9/13/07, Marc Be
Hi SOLR kings,
I'm just playing around with queries, but I was not able to query for
any special characters like the German "Umlaute" (i.e., ä, ö, ü). Maybe
others might have the same effects and already found a solution ;-)
Here is my example: I have one field called "sometext" of type "text
The straightforward solution is to not put your indexes on NFS. It is
slow and it causes failures like this.
I'm serious about that. I've seen several different search engines
(not just Solr/Lucene) get very slow and unreliable when the indexes
were on NFS.
wunder
On 9/13/07 10:59 AM, "Kasi Sank
Hi All,
I have multiple SOLR instances in read only mode accessing index files
on a NFS partition, I run the indexing/updating of indexing from another
SOLR
Instance. When I run a commit command on the search servers to warm up
the searchers after update I get 'NFS stale handle' error message.
Hello!
Can you not facet on fields which are not indexed? Am I missing
something here?
++
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
++
Thanks Matt, I'll give it a try! So this requires JettyPlus?
--
Best regards,
Jack
Wednesday, September 12, 2007, 5:14:32 AM, you wrote:
> Jack, I've posted a complete recipe for running two Solr indices
> within one Jetty 6 container:
> http://wiki.apache.org/solr/SolrJetty
> Scroll down t
Hi,
I am facing a issue with facet fields.
I have one field as category in my schema.xml file and i have mapped it to
facet fields. But the problem is, one of the category is "Repository" which is
displaying fine in category field but in facet field it is showing
"Repositori". y is getting cha
14 matches
Mail list logo