Hi,
I'm trying to index some UTF-8 data, but I'm experiencing some problems.
I'm using the 28th July nightly build, which I believe contains all the recent fixes for
making the administration webapp use UTF-8. I've tried running in both the provided Jetty
instance and Tomcat 5.5.17.
I've ind
On 8/10/06, Andrew May <[EMAIL PROTECTED]> wrote:
...I'm using the 28th July nightly build, which I believe contains all the
recent fixes...
Does your build contain the
http://issues.apache.org/jira/browse/SOLR-38 patch, and if so did you
try posting the utf8-example.xml document with post.sh
Bertrand Delacretaz wrote:
Does your build contain the
http://issues.apache.org/jira/browse/SOLR-38 patch, and if so did you
try posting the utf8-example.xml document with post.sh and querying it
through the admin interface?
That patch should be part of the build I'm using (patch committed on t
I no longer remember when or where this came up, but when using Tomcat
there is a known character encoding problem when you expect utf-8. In
Tomcat's $TOMCAT_HOME/conf/server.xml on the port you're running Solr on
ensure URIEncoding="UTF-8" is in
This has solved some of my encoding problems.
On 8/10/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
FYI, xml.com just published an article that I wrote after testing Solr
in the last few weeks:
"Solr: Indexing XML with Lucene and REST"
http://www.xml.com/pub/a/2006/08/09/solr-indexing-xml-with-lucene-andrest.html
It's basic stuff, but
I'm trying to index data in a system that implements some rather nasty
access controls on the data.
Basically, there are users, and communities, and users are members of
the communities. Potentially a user could be a member of hundreds or
even thousands of communities (there's no enforced upper li
On 8/10/06, Martyn Smith <[EMAIL PROTECTED]> wrote:
I'm trying to index data in a system that implements some rather nasty
access controls on the data.
Basically, there are users, and communities, and users are members of
the communities. Potentially a user could be a member of hundreds or
even
I was just reading about the limit on boolean operators in a query (it
seems to default to 1024 in Solr).
Using option 2 would mean that a user can't be in any more than 1024
communities (assuming no other boolean logic in the query).
Potentially a huge number of communities (10,000+ ?). Each com
On 8/10/06, Martyn Smith <[EMAIL PROTECTED]> wrote:
I was just reading about the limit on boolean operators in a query (it
seems to default to 1024 in Solr).
Using option 2 would mean that a user can't be in any more than 1024
communities (assuming no other boolean logic in the query).
Potentia
We're not really sure how big the userbase is going to get, but it could
become huge. I think initially we need to be able to cope with several
thousand users, and probably only several thousand communities.
I'll certainly have a look at "faceted browsing" :), and yeah, a query
handler that does t
10 matches
Mail list logo
