Hi Aseem -
I had a similar challenge. The solution that works for my case was to
add role as a repeating string value in the solr schema.
Each piece of content contains 1 or more roles and these values are
supplied to solr for indexing.
Users also have one or more roles (which correspond
that help?
On Nov 2, 2009, at 4:37 PM, Glock, Thomas wrote:
Hoping someone might help with getting /update/extract RequestHandler
to work under Tomcat.
Error 500 happens when trying to access
http://localhost:8080/apache-solr-1.4-dev/update/extract/ (see below)
Note /update/extract DOES
Follow-up -
This is now working (sadly I'm not sure exactly why!) but I've
successfully used curl (under windows) and the following examples to
parse content
curl
http://localhost:8080/apache-solr-1.4-dev/update/extract?extractOnly=tru
e --data-binary @curl-config.pdf -H
Hoping someone might help with getting /update/extract RequestHandler to
work under Tomcat.
Error 500 happens when trying to access
http://localhost:8080/apache-solr-1.4-dev/update/extract/ (see below)
Note /update/extract DOES work correctly under the Jetty provided
example.
I think I must
on the user's role. I have only two roles to support, so my case
is very simple, but I could imagine having a multivalued role field
that you could perform facet queries on.
Mark
Glock, Thomas wrote:
Thanks -
I agree. However my application requires results be trimmed to users
based
Hoping someone can help -
Problem:
Querying for non-english phrases such as Добавить do not return any
results under Tomcat but do work when using the Jetty example.
Both tomcat and jetty are being queried by the same custom (flash)
client and both reference the same
12:43 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr under tomcat - UTF-8 issue
Try using example/exampledocs/test_utf8.sh to narrow down if the charset
problems you're hitting are due to servlet container configuration.
-Yonik
http://www.lucidimagination.com
2009/10/24 Glock, Thomas
for search results.
Use GET. That will make it possible to cache the results, will make your HTTP
logs useful, and all sorts of other good things.
wunder
On Oct 24, 2009, at 10:11 AM, Glock, Thomas wrote:
Thanks - I now think it must be due to my client not sending enough (
or correct ) headers
Is a way to POST queries to Solr instead of supplying query string
parameters ?
Some of our queries may hit up against URL size limits.
If so, can someone provide an example ?
Thanks in advance
