Another way to do multi-lingual indexing is to have a separate field
for each language. Solr/Lucene have custom processing for some
languages.
On Sun, Oct 18, 2009 at 12:25 PM, Germán Biozzoli
wrote:
> Thanks Ahmet. Definitely using analyzer appears the english porter as
> the killer ;)
> Regards
Thanks Ahmet. Definitely using analyzer appears the english porter as
the killer ;)
Regards
German
On Sun, Oct 18, 2009 at 7:30 AM, AHMET ARSLAN wrote:
>
>> Hi everybody
>>
>> I have a simple but (for me) annoying problem. I'm happy
>> user of Solr
>> 1.4 with a small collection of documents. Tod
> Hi everybody
>
> I have a simple but (for me) annoying problem. I'm happy
> user of Solr
> 1.4 with a small collection of documents. Today one of the
> users has
> reported that a query returns documents that are
> non-pertinent to the
> expression. I have spanish, portuguese and english text
>
Thanks Yonik!
Cheers
Avlesh
On Tue, Jun 16, 2009 at 7:25 PM, Yonik Seeley wrote:
> On Tue, Jun 16, 2009 at 8:33 AM, Avlesh Singh wrote:
> > Can someone explain this?
> > +myField:"\*" +city:Mumbai gives me all results for +city:Mumbai
> >
> > myField is a regular text field and "*" is not a stop
On Tue, Jun 16, 2009 at 8:33 AM, Avlesh Singh wrote:
> Can someone explain this?
> +myField:"\*" +city:Mumbai gives me all results for +city:Mumbai
>
> myField is a regular text field and "*" is not a stopword.
* and other non alphanumerics are probably being dropped by WordDelimiterFilter.
-Yoni
Can someone explain this?
+myField:"\*" +city:Mumbai gives me all results for +city:Mumbai
myField is a regular text field and "*" is not a stopword.
Cheers
Avlesh
On Tue, Jun 16, 2009 at 10:26 AM, Yonik Seeley
wrote:
> On Tue, Jun 16, 2009 at 12:28 AM, Avlesh Singh wrote:
> >>
> >> Probably th
On Tue, Jun 16, 2009 at 12:28 AM, Avlesh Singh wrote:
>>
>> Probably the analyzer removed the "$", leaving an empty term and causing
>> the clause to be removed altogether.
>>
>
> I predicted this behavior while writing the mail yesterday, Yonik.
> Does it sound logical and intuitive?
It's intuiti
>
> Maybe you can use this method directly or at least mimic it in your
> application:
> ./src/solrj/org/apache/solr/client/solrj/util/ClientUtils.java: public
> static String escapeQueryChars(String s)
>
Does not help either, Otis.
(+myField:"$" +city:Mumbai) at best could get converted into (+m
And here's the debug info:
+myField:"$" +city:Mumbai
+myField:"$" +city:Mumbai
+city:Mumbai
+city:Mumbai
OldLuceneQParser
I found this unintuitive. "No results" rather than "All results" was the
expected behavior.
Cheers
Avlesh
On Tue, Jun 16, 2009 at 9:58 AM, Avlesh Singh wrote:
> Probably th
>
> Probably the analyzer removed the "$", leaving an empty term and causing
> the clause to be removed altogether.
>
I predicted this behavior while writing the mail yesterday, Yonik.
Does it sound logical and intuitive?
Cheers
Avlesh
On Tue, Jun 16, 2009 at 9:42 AM, Yonik Seeley wrote:
> On M
On Mon, Jun 15, 2009 at 11:53 PM, Avlesh Singh wrote:
> How does one explain this?
> +myField:"$" give zero result
> +myField:"$" +city:"Mumbai" gives result for city:"Mumbai"
Probably the analyzer removed the "$", leaving an empty term and
causing the clause to be removed altogether.
-Yonik
http
How does one explain this?
+myField:"$" give zero result
+myField:"$" +city:"Mumbai" gives result for city:"Mumbai"
Cheers
Avlesh
On Tue, Jun 16, 2009 at 12:50 AM, Otis Gospodnetic <
otis_gospodne...@yahoo.com> wrote:
>
> Hi,
>
> It looks like the query parser is doing its job of removing certai
Hi,
It looks like the query parser is doing its job of removing certain characters
from the query string.
Maybe you can use this method directly or at least mimic it in your application:
./src/solrj/org/apache/solr/client/solrj/util/ClientUtils.java: public static
String escapeQueryChars(Str
13 matches
Mail list logo
