We use the PatternTokenizerFactory. We have the following in our
schema:
tokenizer class=solr.PatternTokenizerFactory
pattern=([^a-zA-Z0-9_])/
And to get rid of '_' we just remove it from the pattern.
-Original Message-
From:
Thank you for the responses!
-Original Message-
From: Grant Ingersoll [mailto:gsi...@gmail.com] On Behalf Of Grant
Ingersoll
Sent: Wednesday, February 03, 2010 1:56 PM
To: solr-user@lucene.apache.org
Subject: Re: Guidance on Solr errors
Inline below.
On Feb 2, 2010, at 8:40 PM, Vauthrin
Hello,
I'm trying to troubleshoot a problem that occurred on a few Solr slave
Tomcat instances and wanted to run it by the list to see if I'm on the
right track.
The setup involves 1 master replicating to three slaves (I don't know
what the replication interval is at this time). These
[mailto:solr-user-return-30215-laurent.vauthrin=disney@lucene.apache
.org] On Behalf Of Vauthrin, Laurent
Sent: Thursday, December 10, 2009 11:44 AM
To: solr-user@lucene.apache.org
Subject: RE: SolrPlugin Guidance
Ok, looks like I may not be taking the right approach here. I'm running
a problem
@lucene.apache.org
[mailto:solr-user-return-30170-laurent.vauthrin=disney@lucene.apache
.org] On Behalf Of Vauthrin, Laurent
Sent: Wednesday, December 09, 2009 2:53 PM
To: solr-user@lucene.apache.org
Subject: RE: SolrPlugin Guidance
Thanks for the response. I went ahead and gave it a shot. In my case
Thanks for the response. I went ahead and gave it a shot. In my case,
the directory name may not be unique so if I get multiple ids back then
I create a BooleanQuery (Occur.SHOULD) to substitute the directory name
query. This seems to work at the moment so hopefully that's the right
approach.
Hello,
Our team is trying to make a Solr plugin that needs to parse/decompose a
given query into potentially multiple queries. The idea is that we're
trying to abstract a complex schema (with different document types) from
the users so that their queries can be simpler.
So basically,
Hello,
One of our deployed Solr (1.3) setup is having out of memory issues and
I'm not sure how to troubleshoot it. I've read a few posts (including
http://old.nabble.com/Debugging-Solr-memory-usage-heap-problems-ts883279
4.html#a8832794) but I think this situation is slightly different.
the file where the heap should be dumped. You can then
analyze it and see what's eating the memory.
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
From: Vauthrin, Laurent laurent.vauth
Hello,
I'm having a problem with a query but I don't understand what is wrong
with it. Can someone explain the following?
Here are a few queries that work as expected (premium is a boolean
field):
premium:false-3004
premium:true -0
-premium:false - 0
Looks like I was using the wrong field when searching (tokenized instead
of untokenized) and this approach actually worked. Sorry for the
confusion.
-Original Message-
From: Vauthrin, Laurent
Sent: Monday, April 06, 2009 10:03 AM
To: solr-user@lucene.apache.org
Subject: RE: Wildcard
- Solr - Nutch
- Original Message
From: Vauthrin, Laurent laurent.vauth...@disney.com
To: solr-user@lucene.apache.org
Sent: Monday, March 30, 2009 5:45:30 PM
Subject: Wildcard searches
Hello again,
I'm in the process of converting one of our services that was
previously
using
Are the queries only returning 10 results? (in the result element -
result name=response numFound=10 start=0)
By default, I believe Solr will only return the first ten results it
finds which may explain the results.
-Original Message-
From:
I'm not sure if I did this the right way but here's what I ended up
using:
fieldType name=string class=solr.TextField sortMissingLast=true
omitNorms=true
analyzer
tokenizer class=solr.KeywordTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
Hello again,
I'm in the process of converting one of our services that was previously
using Lucene to use Solr instead. The main focus here is to preserve
backwards compatibility (even if some searches are not as efficient).
There are currently two scenarios that are giving me problems right
Hello again,
I believe that this question has been posed before but I just wanted to
make sure I understood my options. Here's the situation:
We have a few fields that are specified as 'text' and a few field that
are specified as 'string'. As far as I understand, 'string' will do
exact
??? ??
Sent: Tuesday, March 17, 2009 9:04 PM
To: solr-user@lucene.apache.org
Subject: Re: More replication questions
On Wed, Mar 18, 2009 at 12:34 AM, Vauthrin, Laurent
laurent.vauth...@disney.com wrote:
Hello,
I have a couple of questions relating to replication in Solr. As far as
I
Of Yonik Seeley
Sent: Wednesday, March 11, 2009 5:03 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication in 1.3
On Wed, Mar 11, 2009 at 1:29 PM, Vauthrin, Laurent
laurent.vauth...@disney.com wrote:
I'm hoping to use Solr version 1.4 but in the meantime I'm trying to get
replication to work
in 1.3
On Thu, Mar 12, 2009 at 12:34 PM, Vauthrin, Laurent
laurent.vauth...@disney.com wrote:
Just so I'm clear on it, do you mean Windows replication via Cygwin is
not supported or not possible?
Not really possible - the strategy the scripts use won't work on
Windows because of the different
wrote:
We're currently using 1.4 in production right now, using a recent
nightly. It's working fine for us.
Thanks for your time!
Matthew Runo
Software Engineer, Zappos.com
mr...@zappos.com - 702-943-7833
On Mar 10, 2009, at 10:25 AM, Vauthrin, Laurent wrote:
Hello,
I'm not sure
I'm hoping to use Solr version 1.4 but in the meantime I'm trying to get
replication to work in version 1.3. I'm running Tomcat as a Windows
service and have Cygwin installed. I'm trying to get the snapshooter
script to run with the following in my solrconfig.xml:
listener
Hello,
I'm not sure if this is the right forum for this, but I'm wondering if I
could get a rough timeline of when version 1.4 of Solr might be out?
I'm trying to figure out whether we will be able to use the new built-in
replication as opposed to the current rsync collection distribution.
@lucene.apache.org
Subject: Re: Version 1.4 of Solr
We're currently using 1.4 in production right now, using a recent
nightly. It's working fine for us.
Thanks for your time!
Matthew Runo
Software Engineer, Zappos.com
mr...@zappos.com - 702-943-7833
On Mar 10, 2009, at 10:25 AM, Vauthrin, Laurent wrote
23 matches
Mail list logo
