Hi,
I've realized I need to change a particular field from text_ws to text.
I realize I need to reindex as the tokens are being stored in a case
sensitive manner which we do not want.
However can I just reindex all my documents, or do I need to drop/wipe the
/data/index dir and start fresh?
I r
Hi,
I don't understand this at all. We are indexing some contact names. When we
do a standard query:
query 1: capi*
result: Capital Health
query 2: capit*
result: Capital Health
query 3: capita*
result:
query 4: capital*
result:
I understand (as we are using solar 3.5) that the wildcard sea
ent AS - www.cominvent.com
> Solr Training - www.solrtraining.com
>
> On 23. jan. 2012, at 22:26, Wayne W wrote:
>
>> Hi,
>>
>> Im been trying to figure this out now for a few days and I'm just not
>> getting anywhere, so any pointers would be MOST welcome. I
Hi,
Im been trying to figure this out now for a few days and I'm just not
getting anywhere, so any pointers would be MOST welcome. I'm in the
process of upgrading from 1.3 to the latest and greatest version of
Solr and I'm getting there slowly. However I have this (final) problem
that when sending
ining - www.solrtraining.com
>
> On 19. jan. 2012, at 23:08, Wayne W wrote:
>
>> HI,
>>
>> I'm trying to setup the latest version of Solr. Currently we're
>> running 1.3 so we're a bit out of date!
>>
>> Having trouble setting up the tika/
HI,
I'm trying to setup the latest version of Solr. Currently we're
running 1.3 so we're a bit out of date!
Having trouble setting up the tika/extractionhandler jars etc, but I
think I'm nearly there. However I've got this stack trace, thats
complaining about a required field missing. However as
86
>
> Tricia
>
> On Sat, Jan 14, 2012 at 12:53 AM, Wayne W wrote:
>
>> Hi,
>>
>> we're using Solr running on tomcat with 1GB in production, and of late
>> we've been having a huge number of OutOfMemory issues. It seems from
>> what I can tell
Hi,
we're using Solr running on tomcat with 1GB in production, and of late
we've been having a huge number of OutOfMemory issues. It seems from
what I can tell this is coming from the tika extraction of the
content. I've processed the java dump file using a memory analyzer and
its pretty clean at
