Re: getting error when : in the query

However I would also like to know that, is there any short way to put \ before special character which will not effect the performance. There is a static method in org.apache.lucene.queryParser.QueryParser that does this: QueryParser.escape(String s);

Re: multi term, multi field, auto suggest

On 29.01.2010, at 15:40, Lukas Kahwe Smith wrote: I am still a bit unsure how to handle both the lowercased and the case preserved version: So here are some examples: UBS = ubs|UBS Kreuzstrasse = kreuzstrasse|Kreuzstrasse So when I type Kreu I would get a suggestion of Kreuzstrasse

Re: multi term, multi field, auto suggest

On 01.02.2010, at 13:27, Lukas Kahwe Smith wrote: On 29.01.2010, at 15:40, Lukas Kahwe Smith wrote: I am still a bit unsure how to handle both the lowercased and the case preserved version: So here are some examples: UBS = ubs|UBS Kreuzstrasse = kreuzstrasse|Kreuzstrasse So when

Problem in indexing on large data set by Dataimporthandler in solr

Hi, I am trying to index some large set of data in solr using dataimporthandler. It is working fine for small set but when I am trying to index on large set it produces error. I am using solr version 1.3 and mysql version Ver 14.7 Distrib 4.1.20, for redhat-linux-gnu (i686) Earlier

Re: Problem in indexing on large data set by Dataimporthandler in solr

Can you give it a shot on Solr 1.4 instead? DIH has had numerous enhancements/fixes since 1.3. Erik On Feb 1, 2010, at 8:42 AM, Vijayant Kumar wrote: Hi, I am trying to index some large set of data in solr using dataimporthandler. It is working fine for small set but when I am

Re: Wildcard Search and Filter in Solr

hey thanks ravi , ahmed and Erik for your reply. though its tough to change my solr version , still let me try out at 1.4 and see. Erik Hatcher-4 wrote: Note that the query analyzer output is NOT doing query _parsing_, but rather taking the string you passed and running it through the

RE: solr - katta integration

Hi Jason, I looked at your way of integrating katta into solr in issue 1395 and I was trying to understand the architecture of the whole set up . I understand that Solr+Katta nodes talk to each other via Hadoop RPC (provided by Katta). Is the real search being taken care by SOLR and the SOLRs

weird behabiour when setting negative boost with bq using dismax

I already asked about this long ago but the answer doesn't seem to work... I am trying to set a negative query boost to send the results that match field_a: 54 to a lower position. I have tried it in 2 different ways: bq=(*:* -field_a:54^1) bq=-field_a:54^1 None of them seem to work.

Fwd: machine tags, copy fields and pattern tokenizers

Hi, Just a quick note to mention that I finally figured (most of) this out. The short version is that if there's an explicit index analyzer (as in type=index) but not a corresponding query analyzer then Solr appears to use the first for all cases. I guess this makes sense but it's a bit

Re: Contributors - Solr in Action Case Studies

Hello everyone, Thanks to all who emailed me so far. This is just another reminder for those who missed the first email below. Please let us know if you'd like to contribute a piece to Solr in Action about your interesting use of Solr. Thanks, Otis Sematext :: http://sematext.com/ ::

DataImportHandler delta-import confusion

First, let me just say that DataImportHandler is fantastic. It got my old mysql-php-xml index rebuild process down from 30 hours to 6 minutes. I'm trying to use the delta-import functionality now but failing miserably. Here's my entity tag: (some SELECT statements reduced to increase

query on not stored field

Hi on the following field fields name=status [...] field name=message index=analyzed store=yes default=true/ [...] /fields the following query works {!lucene q.op=AND} [...] AND (status.messageSTRING_ANALYZED_NO_US:(some keywords) AND [...] I was wondering If the query syntax above works as

Re: query on not stored field

field name=message index=analyzed store=yes default=true/ Both index=analyzed and store=yes are not parsed by Solr schema. Use indexed and stored instead of index and store, and set either true or false. Koji -- http://www.rondhuit.com/en/

Re: query on not stored field

First of all, the schema snippets you provided aren't right. It's indexed=true, not index=analyzed. And it's stored, not store. But, to answer your question, the stored nature of the field has nothing whatsoever to do with it's searchability. Stored only affects whether you can get that

Indexing a oracle warehouse table

Hello all, hope someone can point me to right direction. I am trying to index an oracle warehouse table(TableA) with 850 columns. Out of the structure about 800 fields are CLOBs and are good candidate to enable full-text searching. Also have few columns which has relational link to other tables.

Re: query on not stored field

Koji, Eric Thank you for your reply One more question: What about a field that is both indexed=false stored=false ... does it have an impact into solr meaning is it being ignored by solr/lucene? is it like the field was not being passed? Thank you! --- On Mon, 2/1/10, Erik Hatcher

Re: query on not stored field

On Feb 1, 2010, at 8:45 PM, Matthieu Labour wrote: What about a field that is both indexed=false stored=false ... does it have an impact into solr meaning is it being ignored by solr/ lucene? is it like the field was not being passed? Yes, that's a trick in Solr to ignore a field. The

Solr and location based searches

Hi all, We want to use Solr because of its facet based functionalities... now the customer want to combine searches based on facets with location based searches (all objects 10 miles around this particular zip)... Is this possible in Solr or is there no way? Thanks and best regards, Sandro